If you've ever read that silly screencap comic about The Lord of the Rings, you probably know who Shamus Young is. You probably also know that he's a pretty good writer, definitely entertaining, sometimes wickedly funny, and 101% geek.
So, in keeping with the reference to the Doom code review from earlier, here's Shamus with Coding Style Part 1:
Three layers of indirection.
"Forget it. We go any deeper, we just raise the stakes. I am sitting this one out on this level, boys."
So, in keeping with the reference to the Doom code review from earlier, here's Shamus with Coding Style Part 1:
I think most software companies have a set of rules for writing and formatting code. This is often referred to as a “style guide”. This tells the programmers on staff how to make code that will fit together in a coherent system...
It’s pretty common to write code and then forget what it does or how it works. So when you’re writing code you should always be thinking of the other programmer. The dumb programmer. The programmer who doesn’t understand this code and has no idea what’s going on. The odds are very good that this other programmer is going to be a future version of you.Haven't read it yet, so... let's see. That makes for one article on a particular coding style that I want to read; an article about coding styles in general that I want to read; and... um, this blog post, in which I write about articles about coding style.
Three layers of indirection.
"Forget it. We go any deeper, we just raise the stakes. I am sitting this one out on this level, boys."
No comments:
Post a Comment