Linked by Thom Holwerda on Fri 15th Feb 2013 10:40 UTC
General Development "Since I left my job at Amazon I have spent a lot of time reading great source code. Having exhausted the insanely good idSoftware pool, the next thing to read was one of the greatest game of all time: Duke Nukem 3D and the engine powering it named 'Build'. It turned out to be a difficult experience: The engine delivered great value and ranked high in terms of speed, stability and memory consumption but my enthousiasm met a source code controversial in terms of organization, best practices and comments/documentation. This reading session taught me a lot about code legacy and what helps a software live long." Hail to the king, baby.
Permalink for comment 552841
To read all comments associated with this story, please click here.
RE[2]: Comment by ilovebeer
by ilovebeer on Mon 18th Feb 2013 20:55 UTC in reply to "RE: Comment by ilovebeer"
Member since:

There doesn't exist a situation where code doesn't need maintenance. Assuming so is a stunning display of a lack of forethought.

Of course there is. Just like there are situations where code needs little maintenance, and where code needs considerable maintenance. Assuming all code needs maintenance is the true stunning display of poor assumption. I guess there are people who haven't heard of backwards-compatibility, not breaking user-space as rule of thumb, ABI, etc. Or that the code is simplistic enough that no changes have been needed in ages (if ever).

Reply Parent Score: 2