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 552726
To read all comments associated with this story, please click here.
Comment by ilovebeer
by ilovebeer on Sat 16th Feb 2013 06:06 UTC
Member since:

Arguing over coding styles is many times just as stupid as arguing over which OS is best. Whether "you" like it or not, what matters most is (as previously stated) whether the program does what it's meant to do and is stable.

If nobody needs to read the code, who cares how readable it is. If nobody needs to add things to it, who cares how readable it is. If nobody needs to maintain it, who cares how readable it is.

In all honestly, a lot of the people who whine about coding style have terrible coding style of their own. Not to mention don't have design/vision to really optimize anything.

Reply Score: 1