Timeline for How would you know if you've written readable and easily maintainable code?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2017 at 3:20 | comment | added | Wildcard | Your final paragraph mentioning the drawbacks of McCabe score divided by LOC rather tends to invalidate the whole idea. If you need 300 paths through your code, why on earth do you think it will make the code more maintainable to use more lines? That's like saying that if a book presents intricate ideas, it should be a really big book rather than trying to communicate concisely. -1. | |
| Jun 20, 2014 at 14:36 | comment | added | Jon Raynor | This should be the answer. Measure. Other answers are more opinion than fact, if I can understand it, it must good? First measure using complexity analysis, then human refactor to look for duplication, etc. | |
| Mar 26, 2014 at 10:08 | history | edited | Calphool | CC BY-SA 3.0 | grammar fix |
| S Mar 26, 2014 at 2:14 | history | answered | Calphool | CC BY-SA 3.0 | |
| S Mar 26, 2014 at 2:14 | history | made wiki | Post Made Community Wiki by Calphool |