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.
Thread beginning with comment 552824
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Sorry but NO.
by Nelson on Mon 18th Feb 2013 18:12 UTC in reply to "Sorry but NO."
Member since:

Guidelines are loosely applicable, so while its great you can find a corner case, it doesn't really mean much.

No guideline applies 100% in every situation, there are always exceptions. The programmer needs to be aware of the constraints he operates in and adjust accordingly.

Similarly in resource strapped environments like mobile, sometimes you sacrifice good design to achieve acceptable performance. Its not nice, and pie in the sky academics probably scoff at it, but its reality.

Reply Parent Score: 3