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

The processors have also become too complex:

- out of order execution
- parallel execution units
- branch prediction
- multiple cache levels
- opcode rewriting
- (put you favourite feature here)

You need to be super human to really optimize for a given processor given all the variables, and when you manage to do it, it is only for a specific model.

Only on the embedded space it is still an advantage to code directly in assembly.

Reply Parent Score: 4