Comment Re:Oh great... (Score 5, Funny) 224
Fail to convert back and forth between...
Fail to convert back and forth between...
When you're competing with someone who doesn't check anything they put up, you start to look pretty follow-the-leaders when you post after fact-checking
So maybe they're doing it wrong? Not every article has to be breaking to be worthy. You don't always have to be first. Remember, news aren't made by journalists, it's covered by them, and newsworthy stuff happens regardless of whether anyone covers it. The obsession with being first is putting the cart before the horse. Do proper fact-checking and be a better source of news, it's that simple. Oh, and dropping the obvious party affiliations would go a long way too.
Heat kiddo. You know it's still water even if we call it ice in it's solid phase right? Just like steam is also just water.
It could be down from 300 or any other arbitrarily chosen number. There are 19 insurers involved, I doubt they landed on the 201 on their first meeting.
Beautiful.
You do not badmouth your former employer, no matter what they did.
And had she not done so, you would still be able to read the quoted statement, right? Wrong. Nothing happens if people don't speak up, and if it has to be in a public statement about the hows and whys, so be it. It can only be construed as illoyal or unprofessional if your first course of action is whining on the Internet. That is not what happened, according to both Julie and GitHub.
Suing is not going to fix the problem, it is most likely to end in a dismissal or a settlement (with an NDA), both outcomes less than ideal for the other employees.
If your company culture is so sick, that it cannot survive the light of day, I'm not sure you deserve to hire Julie, or anyone else for that matter.
Well, they might. Or maybe it's a sign of the end times, a sign that the righteous must arm themselves. Who the fuck knows with these people?
I don't know. And if they did, which of the bugs were fixed? Is it possible that there could be even more? I simply don't know. I scrapped it all for unrelated reasons and moved on, but it haunts me still - were there 2 or 3 bugs when the comment was made?
I delete more comments than I make. One place it's some guys initials and nothing else, another just has the word "bug" and a date, some are clearly wrong or outright betray a fundamental lack of understanding. Hence the qualification that the comment had to be correct. Incorrect comments are the bane of all existence, and in that context I would prefer no comment at all.
But working with this crap all day, and then coming across a comment that is both short, and accurate, even if it is blindingly obvious that Math.Round does in fact round numbers, is sweet relief.
Yes indeed, the massive wall of empty XML tags approach to commenting. I've got an ample supply of those too, "I'll do it later I swear, I just did it to shut up the build agent!".
Expected state at start
Guaranteed state at finish
Gnarly hacks to keep an eye on
Keep the rest in your notebook and refactor the code until you don't need the notes anymore.
In an ideal world without clueless bosses, deadlines and working with less than perfect colleagues (ourselves included), sure.
I'll take a correct comment over no comment any day. Characters are free and much of the code I am forced to look at on a daily basis, was written by a monkey and comes in chunks of 1000+ lines of spaghetti. A comment, however trivial, that is also correct, is like a beautiful, naked and horny woman, with her heart set on fucking you senseless (or whatever passes for hot in guys these days, if that's your thing).
one_letter_identifier = other_one_letter_identifier + (complex_and_wrong_calculation) / (could_possibly_be_zero)
Is fixing the bug! (I shit you not, I have come across that very statement in production code, except for the variable naming).
It has always pissed me off that they thought it would be cool to hijack the name in an effort to be clever, since it falls flat on it's face for 99.99% of the world's population. And even if you happen to find a Dane and ask him about Harald Blue Tooth, chances are pretty good that the only things he'll know are
a) He was some kind of Viking King.
b) He had a blue tooth.
c) According to legend he got duped by a priest into accepting Christianity, using a wet towel, a camp fire and a miraculous healing.
d) He was the father of our nation, maybe, or maybe it was one of the other 100 pillaging barbarians we get taught about in school.
Not only is it an insult to our cultural heritage, since the Bluetooth standard is a piece of shit, but it's understandable by so very few that even Danes will mention the origin of the name as a kind of party-fact and everyone will go "oh, wow".
Apathy is an acceptable outcome for a propaganda machine.
1 + 1 = 3, for large values of 1.