Timeline for How would you know if you've written readable and easily maintainable code?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2015 at 7:43 | comment | added | amrx | True, if the code is written without a comment. but the issue here can be if the code is commented but yet not understandable or explicit for other developers. | |
| Sep 22, 2014 at 17:16 | comment | added | Jake Toronto | @deworde sometimes code takes time to understand and follow. Not all algorithms are created equal: by the nature of the problem they are trying to solve, they are simply more difficult. | |
| Sep 2, 2014 at 14:22 | comment | added | djechlin | @MichaelDurrant it still kind of is, since you can learn what unclear things you were doing six months ago, and not do those things today. | |
| Mar 17, 2014 at 16:19 | comment | added | dj18 | @MichaelDurrant Each time you review old code you'll find pieces that should have been written differently and then you'll take that into account for the code that you're writing "today". Yes, it does take time to learn how to write good code. | |
| Apr 18, 2012 at 21:31 | comment | added | Evan Plaice | I just got done migrating a bunch of my old (3yrs) code from PHP to python. Surprisingly, even though I knew about 5% about software development that I know now it was surprisingly readable. OTOH, the HTML/CSS... WTF!!! | |
| Apr 18, 2012 at 12:59 | history | made wiki | Post Made Community Wiki by JohnFx | ||
| Mar 28, 2012 at 5:48 | comment | added | Lazy Badger | @ThorbjørnRavnAndersen - yes, with some limitations: I can forgot source language in order to be able to write (not read "for getting overview") and haven't base to debug | |
| Mar 27, 2012 at 21:52 | comment | added | user1249 | @LazyBadger but can you change it? | |
| Mar 23, 2012 at 15:14 | comment | added | Chris Bye | I might drop the timeframe for revisiting down to a month, or even less, for a first revisit. I think it depends on the complexity of the project and domain, as well as your mental approach. I find that in six months, I get distracted by seeing refactoring or optimization opportunities using tools or techniques I've learned since i first wrote the code, instead of real readability. | |
| Mar 23, 2012 at 9:06 | comment | added | deworde | Dissection suggests it's taking a while and you have to do it carefully... | |
| Mar 22, 2012 at 22:46 | comment | added | Lazy Badger | I can read and dissect any and all my code from 1990. Am I God of Programming? | |
| Mar 22, 2012 at 18:05 | comment | added | Michael Durrant | Yeah, that sounds good (and is true), but it's not a very good approach for deciding what/how to do today... | |
| Mar 22, 2012 at 16:55 | history | answered | Alex In Paris | CC BY-SA 3.0 |