Slashdot Mirror
Auto Code Commenting Software, Free Chairs
sien writes "When you think about it, code is usually fairly mundane and simple. Finally someone has come up with a parser and lexer that actually auto-comments code, allowing for vastly more rapid coding. This amazing new tool is called The Commentator and claims to analyse source code as it's being written and insert the necessary code comments. It's absolutely amazing. Also the problem of seating for eXtreme Programming has finally been solved."
Beauty, this will replace the legions of QA people that used to do my code commenting
The rock, the vulture, and the chain
I wonder if it will read the code commentary aloud in John Madden's voice for extra money?
If brevity is the soul of wit, then how does one explain Twitter?
Perhaps it will be opposite this year? Picking the true article out of the heaps of really bad fakes?
You don't exist. Go away.
Analogies don't equal equalities, they are merely somewhat analogous.
Sadly, that is the only chair big enough for some men's asses...
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
Every year slashdot does this, every year people complain. The joke is being fooled into complaining. The joke is people revisit the site like every normal day hoping for it to end and it doesn't. The editors are having a laugh at YOUR expense and you don't even know it.
Relax, go over to Fark, who's random joke page can actually be amusing and read about the Pope being note quite dead yet and come back to Slashdot tomorrow. If you actually miss anything real, you can read it then.
Burn Hollywood Burn
//TODO: remove this comment
word.
I guess we'd better cancel Sense of Humor Day too, then.
...and it's just not true.
/* FALLTHROUGH */ can tell sourch code analyzers such as Lint some useful information too. (Not to mention the programmer that looks at your code and has to think for a sec "did he mean to leave out the break there?")
Good variable names (class names, function names, etc.) go a long way: they tell you a lot about WHAT the program is doing. (I would argue that they can't always say everything too, but that's another matter.)
However, they don't tell you WHY you are doing what you are doing.
Also, remember there are other reasons for comments besides people reading your code. JavaDoc/Doxygen comments allow documentation to be produced right from the source. Comments such as
Good code doesn't require comments - the variable names should tell you everything you need to know about the program.
You must be the guy that made the database at the last place I worked! The column names were complete sentences, including spaces and punctuation (it had never occurred to me that you could even do that). It was a real bitch to work with. Find the middle ground.