The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
While I personally too prefer to read code, rather than comments (especially since the compiler checks my code but not my comments), I don't mind the occasional meaningful comment (although I am eager to delete comments when I spot them, provided the code they explain is self-describing). But stuff like the // parses the date in the post above, or } // code block ends here are IMO just a sign of sloppiness and lack of understanding of what comments are really for.
Yeah but that's an extreme case.... the other side of that is someone who assumes that all their code is readable and interpretable by other people. An engineer that I'm working with now is really bothered by the fact that someone used "fs" to stand for file something or another (can't remember exactly) but to those of us in telecommunications, that's usually used for sampling frequency.
In another words, your self-commenting code might not mean the same thing to someone else, so just be mindful of that.
He was probably raging at the elephanting sunshine who wrote the >1000 line method with broken indenting; and the coding policies that forbid making anything beyond the minimum possible change to fix a bug/implement a feature (meaning whitespace fix, or breaking into 20 smaller logical functions).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
We have JIRA too. It's rubbish, but infinitely preferable to what we had before which was somebody coming over and taking a maximum of 3 seconds to verbally communicate a month's work, only to forget what it was as soon as they leave the room.
I liken most of my fault reports to the captain of the QE2 docking the ship, walking down the gangplank, saying "something's not working", and walking away, expecting you to (a) instantly grasp where the problem is (b) know exactly what to do to fix it and (c) fix it yesterday.