Slashdot Mirror
Comment Profanity by Language
beret found a nifty little pie chart breaking down
profanity in code comments broken down by language. He used Carlin's Seven Words, and C++ came out on top while PHP users are either wholesome or perfect.
← Back to Stories (view on slashdot.org)
In my personal opinion, developers like you are the reason why every single 'working' piece of Python code I've encountered has required me to spend time debugging it before actually using it.
I am TheRaven on Soylent News
Then you're doing it wrong -- at the point you can no longer grok what's going on, you've used too much of the feature (for your current level of ability to work with it).
And this holds for the language itself, which is what is usually leveled against. Until you understand what the compiler is doing behind the scenes, don't use it. It doesn't just translate your high-level code, it also can generate a lot of code for you. You have to know what your tools do. Even if the basic way you use them look a lot like how you use other, simpler tools.
Attention zealots and haters: 00100 00100
Most people skilled in a language (yes, even perl) can figure out what a piece of code actually does given enough time to look through it. The comments are to tell us what the code is *supposed* to do and *why*, so when we need to debug it we know what you were thinking when you wrote it and what you were trying to accomplish. When you're trying to figure out why a piece of code doesn't do what it's supposed to do, it's very helpful to know what it was supposed to do first.
Erm, how did you know it wasn't doing what it was supposed to do if you didn't first know what it was supposed to do?
Strange things are afoot at the Circle-K.
C++ Templates will turn the most pious programmer into a curse-slinging, chain-smoking alcoholic.
Only those who don't understand them.
Learn a functional programming language, and you'll understand much more about C++ template programming.
The Tao of math: The numbers you can count are not the real numbers.
The original comment still stands - most PHP "programmers" I know couldn't tell the difference between source control and birth control.
What kind of stupid argument is that? Sure, a lot of people who claim to write PHP code don't know what source control is. But, again, these are commit messages. What percentage of people writing commit messages do you think know what source control is?
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
More like they never fucking comment their motherfucking code.
Perl programmers never put in profane comments, because cursing in Perl itself is much more satisfying.
There's a perfectly reasonable explanation for all of this: PHP is a web language, whereas everyone knows that most curses-based programs are written in C or C++.
Crumb's Corollary: Never bring a knife to a bun fight.
What percentage of people writing commit messages do you think know what source control is?
Sadly, far less than logic would dictate.
Php showed up as perfect because it is almost perfectly comment free.
This is an indictment of the language, not the programmers, since well-commented php is drastically slower (like .5% tomg!) than stripped down and nearly obfuscated code. That fraction really adds up when you have all those unnecessarily dynamic web pages to generate.
Now if someone were to do a comparison on the ratio of active code, to code that is commented out but not removed because the author doesn't use version control... In that category PHP would freaking rule!
Innocent people shouldn't be forced to pay for inferior software development.
--"Code Complete" Microsoft Press