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 552624
To read all comments associated with this story, please click here.
RE[3]: Code Review
by Alfman on Fri 15th Feb 2013 14:56 UTC in reply to "RE[2]: Code Review"
Alfman
Member since:
2011-01-28

moondevil,

"After a few sessions of off-shore code review, one really stops caring about code quality as long as what was requested works."

With all due respect, -10 ;)
I've dealt with too much bad code to write it off as ok as long as it works...

Obligatory link to the obfuscated c contests:
http://ioccc.org/years.html

Incidentally, I wish these contests would focus more on algorithmic obfuscation rather than source code obfuscation. I am not impressed with code that's unreadable because of shortened variable names and whitespace elimination. The best obfuscated code is code which is still incomprehensible even though it uses proper whitespace conventions and comments ;)

Reply Parent Score: 5