http://karpoke.ignaciocano.com/tags/cpp/Recent content in Cpp on Karpoke - Just Another BlogHugo -- 0.167.0esSun, 08 Feb 2015 19:25:00 +0100http://karpoke.ignaciocano.com/2015/02/08/the-exceptional-beauty-of-doom-3s-source-code/Sun, 08 Feb 2015 19:25:00 +0100http://karpoke.ignaciocano.com/2015/02/08/the-exceptional-beauty-of-doom-3s-source-code/<blockquote> <p>What would ”nice looking”—or ”beautiful”, for that matter—actually mean when referring to source code? I asked some programmer friends what they thought that meant. Their answers were obvious, but still worth stating:</p> <ul> <li>Code should be locally coherent and single-functioned: One function should do exactly one thing. It should be clear about what it’s doing.</li> <li>Local code should explain, or at least hint at the overall system design.</li> <li>Code should be self-documenting. Comments should be avoided whenever possible. Comments duplicate work when both writing and reading code. If you need to comment something to make it understandable it should probably be rewritten.</li> </ul> </blockquote> <p>» Shawn McGrath | <a href="http://kotaku.com/5975610/the-exceptional-beauty-of-doom-3s-source-code">kotaku.com</a></p>