Linked by Thom Holwerda on Fri 15th Feb 2013 10:40 UTC
"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 552766
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2006-05-09
When looking at code of running software, it is generally "ugly"; but at difference of the beautiful code, it showed it works and scales.
We always forget the fact that we are reviewing code that has been several times modified by several people in order to add new functionality, fix some issues, work in other scenarios or improve the performance.