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 552610
To read all comments associated with this story, please click here.
RE: Code Review
by Laurence on Fri 15th Feb 2013 13:57 UTC in reply to "Code Review"
Laurence
Member since:
2007-03-26

I have a love/hate relationship with articles like these.

On the one hand it's great to promote readable code, but sometimes I think people get too hung up on what they deem as perfect syntax and can sometimes miss the point of those clever optimisations.

It's a bit like grammar Nazi's who love to correct peoples comments but rarely read deep enough into those posts digest the content being explained.

So I guess what I'm trying to say is that it's good to be reminded about preferred programming practices, just as long as we don't forget the other criteria (usability, performance (if applicable), deadlines)

Edited 2013-02-15 13:59 UTC

Reply Parent Score: 11