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 552945
To read all comments associated with this story, please click here.
RE[5]: Comment by ilovebeer
by Alfman on Tue 19th Feb 2013 17:15 UTC in reply to "RE[4]: Comment by ilovebeer"
Member since:


"Code being difficult to maintain can be the result of a bad programmer doing the job, where the code itself isn't the actual problem but rather your lack of ability is."

You are throwing around these underhanded insults implying that we're bad coders if a piece of code gives us trouble, but the truth is that even good coders have trouble with bad code. What's the deal with wanting to defend bad code?

Reply Parent Score: 2