Linked by Thom Holwerda on Tue 15th Jan 2013 21:24 UTC
General Development "I was really excited to write this article, because it gave me an excuse to really think about what beautiful code is. I still don't think I know, and maybe it's entirely subjective. I do think the two biggest things, for me at least, are stylistic indenting and maximum const-ness. A lot of the stylistic choices are definitely my personal preferences, and I'm sure other programmers will have different opinions. I think the choice of what style to use is up to whoever has to read and write the code, but I certainly think it's something worth thinking about. I would suggest everyone look at the Doom 3 source code because I think it exemplifies beautiful code, as a complete package: from system design down to how to tab space the characters." John Carmack himself replies in the comments.
Thread beginning with comment 549034
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Good article
by WorknMan on Wed 16th Jan 2013 16:32 UTC in reply to "RE[4]: Good article"
Member since:

A basic example is a 'trim' command. The following will remove spaces from the start and the end of the string:
However it's actually computationally less efficient then having two separate replaces:

On the other hand, why not have a goddamn Trim function? It's infinitely more readable than any of this 's/' crap. You're trying to make excuses for a write-only language who's code looks like line noise by saying, 'Well, a good programmer should be able to read line noise' ;)

Edited 2013-01-16 16:35 UTC

Reply Parent Score: 2