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 552672
To read all comments associated with this story, please click here.
RE[4]: Code Review
by moondevil on Fri 15th Feb 2013 19:39 UTC in reply to "RE[3]: Code Review"
Member since:

In my defence there is not much you can do about it, when you have an offshore team of 60 - 100 developers producing new code every day, while you have 5 guys doing development on the customer site.

There is no way to keep up with it.

Reply Parent Score: 3