Timeline for Cost of maintenance depending on paradigms
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2012 at 12:39 | comment | added | Wayne Werner | You mean segments of unstructured programming scattered throughout your code? My young experience (having now 1.5 years of professional programming under my belt) echoes what I wrote. Any amount of deviation from <insert sensible paradigm here> will cause horrible maintenance issues. When I look back at my own code, I can tell you where I deviated because I really have to think and figure out why the heck I did something. When you have and adhere to good standards, code comprehension is as easy as it possibly can be. | |
| Nov 16, 2012 at 18:28 | comment | added | alehro | I'd called thoughts like 'Any sensible paradigm, done right, will give you good maintenance results.' as unstructured thinking. What about quasi-unstructured programming ? Is it good or not? | |
| Apr 10, 2011 at 23:00 | history | answered | Wayne Werner | CC BY-SA 3.0 |