Timeline for How would you know if you've written readable and easily maintainable code?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 19, 2017 at 8:13 | comment | added | Jakub Arnold | I've run countless times into code that was DRY and SOLID and yet horrible. Following principles can give false impression that what you're writing isn't crap. | |
| Jun 16, 2013 at 2:34 | comment | added | Erik Reppen | IMO, SOLID is overrated. Especially the 'S.' That or everybody misreads it. | |
| Apr 18, 2012 at 12:59 | history | made wiki | Post Made Community Wiki by JohnFx | ||
| Apr 5, 2012 at 6:54 | comment | added | user1249 | "If the answer is yes, then the code is readable" ... by you. To see if it is readable to others, others must try reading it. | |
| Mar 22, 2012 at 17:39 | comment | added | DeadMG | This is not a particularly good test. Many applications of those rules are subjective, and you can almost always read your own code right after it's been written. | |
| Mar 22, 2012 at 17:01 | comment | added | jcmeloni | ...and after you read it, hand it to someone else to try to read. | |
| Mar 22, 2012 at 16:55 | history | answered | Oded | CC BY-SA 3.0 |