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 552823
To read all comments associated with this story, please click here.
RE: Comment by ilovebeer
by Nelson on Mon 18th Feb 2013 18:10 UTC in reply to "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.

I've been in many a situation where I've had to maintain code where the original writer was no longer apart of the company.

It is also important to make a distinction between people who want thoughtful and concise design vs people who complain about the spacing of tabs and the line the curly brace goes on.

The latter group are just a bunch of annoying pedants, but the former is an important end to strive towards.

Reply Parent Score: 3