Re:ASK HN: How are you becoming a better programmer?
by hga on Wednesday February 17, 2010 @12:34PM
(#1131932)
Can't believe I forgot this one:
Don't just read code, reanimate it!
Find a large and dead (abandoned) body of code, one where you're not in a position to get much if any help from someone who had a hand in writing or maintaining it, and bring it back to life (e.g. get it running on current systems or a different system).
That makes the difference between simply reading code and really learning the code. Do enough "software archeology" and you'll be able to do all sorts of things: figure out within a few minutes the likely quality of a large body of code, recognize the different people who wrote or changed different parts of it (as in person A, person B...), learn that comments are at best what someone hoped at one point in time what some code would do, etc.
Don't just read code, reanimate it!
Find a large and dead (abandoned) body of code, one where you're not in a position to get much if any help from someone who had a hand in writing or maintaining it, and bring it back to life (e.g. get it running on current systems or a different system).
That makes the difference between simply reading code and really learning the code. Do enough "software archeology" and you'll be able to do all sorts of things: figure out within a few minutes the likely quality of a large body of code, recognize the different people who wrote or changed different parts of it (as in person A, person B...), learn that comments are at best what someone hoped at one point in time what some code would do, etc.