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 553263
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[9]: Code Review
by Alfman on Wed 20th Feb 2013 19:30 UTC in reply to "RE[8]: Code Review"
Alfman
Member since:
2011-01-28

phreck,

"It is not that simple actually. I've seen assembly level programmers who really know what they do, and they do it well, however, that usually was at the micro-optimization level, which doesn't scale to long-lived and/or big softwares."

This is it in a nutshell, large projects cannot be written in assembly any more. But it can still be used effectively to tune pieces of a larger project.


"All in all I am not sure if you are evangelizing Assembly, C or compilers in your post."

You weren't addressing me, but I strongly prefer C. The only time I ever consider assembly is with code that I'm already benchmarking and have identified performance deficiencies. But I try to get the most out of the C version before resorting to assembly code.

Reply Parent Score: 2