Dear Boost developers, We have undertaken a task to assess code complexity triggers and generate recommendations for developing simple and understandable code. Our intension is to share the results with you, developers, so everyone can learn the triggers behind complex software. We need your help for rigorous results. My request to you is - if you get 5-10 min. time, would you please consider to answer the questions of this survey on code complexity? https://goo.gl/forms/h9WXZ8VSEw7BUyHg1 You are welcome to learn preliminary results through this link: https://www.facebook.com/SoftwareCodeQuality/photos/?tab=album&album_id=1639816749664288 The results will be shared in a public webpage and everyone possible will be invited to learn and discuss them. Your knowledge and experience is vital for achieving substantial and generalizable results, and your effort is much appreciated! Sincerely Vard Antinyan PhD candidate in University of Gothenburg, Sweden Tel: 0046317725707
Hi, Am 19.09.2016 17:43, schrieb Vard Antinyan:
The results will be shared in a public webpage and everyone possible will be invited to learn and discuss them.
I think, you should have preferred to have a discussion on the kind of questions first. For most of them, the answer is: "it depends on how you use that." E.g. The length of vairable names is mostly irrelevant. What is more important is how good they identify the semantics. Operators are great, when their semantics for the objects in question are intuitive and horrible otherwise. Many Method calls cann tell the storry, when their names are well chosen. Otherwise they can distract the reader. Frequent changes are no issue, when they are part of a clean test-fix-reactor-cycle. etc. etc. So I am sorry, I can not reasonably answer your questions. Christof
participants (2)
-
Christof Donat -
Vard Antinyan