Disclaimer: You are looking at a post I wrote some time ago. The information and opinions contained within may be outdated and may differ from my current views. Please proceed accordingly.

Subtext and Code Comments

Feb 16, 2004 8:49 PM
Tags:

This kuro5hin piece on what code comments really say about a program is an interesting analysis of the stolen Microsoft source code.

In the struggle to meet deadlines, I think pretty much all programmers have put in comments they might later regret, including swearwords and acerbic comments about other code or requirements. Also, any conscientious coder will put in prominent comments warning others about the trickier parts of the code. Comments like "UGLY TERRIBLE HACK" tend to indicate good code rather than bad: in bad code ugly terrible hacks are considered par for the course. It would therefore be both hypocritical and meaningless to go through the comments looking for embarrassments. But also fun, so let's go.

FWIW, our codebase has no shits or fucks and only one crap — courtesy of a character-converting utility.


Comments: Subtext and Code Comments

I've been waiting to read this article all week, but my client's webfilter won't let me. It also filters out the words "shit" and "fuck" from your site.

Grrrr.

Posted by: Alan Green on February 18, 2004 7:41 AM | permalink

Maybe you can read the Google cache?

http://216.239.39.104/search?q=cache:l96FRh5bah4J:www.kuro5hin.org/story/2004/2/15/71552/7795+%0D%0A&hl=en&ie=UTF-8

Posted by: Joe Grossberg on February 18, 2004 8:35 AM | permalink

No more comments! Either someone has violated Godwin's Law, I'm tired of the discussion or, most likely, the ten-week window has closed. You can, however, contact me through email.