Either date- or version-based. "Delete after dd-mmm-yyyy" or "Commented out in 5.1". (Note how cleverly I avoid anticipating future version numbers. Management tends to change those things.)
To all the people saying "version control": I've seen enough botched configuration-management system changes and moronic branch management to know it ain't the be-all people think it is.
:) Ok, tiger, good one. Made me laugh (but quietly, since I'm in a cube farm).
I can guarantee you no one on my team (of developers, of varying ages) knows what mind maps are, except our BA, who got handed one by someone on ANOTHER team.
It's not management. It's not lack of financial incentive. Mgmt doesn't have time/energy to scrutinize docs, and paying for docs is stupid because you'll get filler.
It's thought leaders on the team. You get some architect who wrote the system and fully understands it, PLUS he's smart, PLUS he's a git r done type (remember? remember? smart, gets things done? Thank you, Joel Spolsky). Result: the smart guy everybody looks to writes no docs. He doesn't need them. It doesn't occur to him that others might need docs, because it's not an immediate problem (fire, crisis) he can put out and be a hero. It's friction. No payoff for him to eliminate _that_.
So, everybody on the team follows his lead. There's no team culture of helping each other out by writing little love notes to each other that say such sweet things as "Returns the two highest priority items that are neither red nor flibbertygibbits (<see cref="isFlibbertyGibbit()"/>)."
What I said was: No, the sad thing is there are people who think it's laudable to score humor points by stylishly saying they don't care and neither should anyone else.
But I do have something to say about the immediate response of "QA". These are design issues (as has been mentioned). QA is not where you test out that sort of thing. Up-front design (not necessarily Big) should be the first response. Now is not the time to slack off on design, just because a lot of the components have already been written.
Development is also a cost center. Those whiners are constantly bitching about architecture. That's why we look for cheap developers who won't raise objections or otherwise make waves (like, with bright ideas), they'll just code. It's just a simple matter of programming, what the heck is up with them, anyway?
He's not a troll. If you search on "hackingbear" you can see that he's (probably) just some Chinese adolescent who's fallen for the nationalist line that problems in the U.S. mean China is no worse off.
Anthony Wiener's shens ==> it's ok to lock up dissidents in China. QED.
(1) Both IE and the Bing toolbar are from MS. Doesn't matter whether they use one or the other; the directive at MS has come down from on high: use Google's results.
(2) The Google search results are only one input into MS's algorithm (they shouldn't be an input/at all/.) Of course all 100 honeypots won't show up. The fact that any did at all is incriminating, given that the data is completely synthetic.
I understand the technologies for both of those things have been lost. (Apparently, the Romans had some trick they did with oxhairs or sinews or something that gave their ballistas a lot more power than the competition.)
Slashdot Mirror
Huh. No wonder Stuxnet was such a success.
If you don't have any, write some. If it's crap, improve it.
Either date- or version-based. "Delete after dd-mmm-yyyy" or "Commented out in 5.1". (Note how cleverly I avoid anticipating future version numbers. Management tends to change those things.)
To all the people saying "version control": I've seen enough botched configuration-management system changes and moronic branch management to know it ain't the be-all people think it is.
That is all.
+1
Bingo.
Plus server in closet for when you need horsepower.
:) Ok, tiger, good one. Made me laugh (but quietly, since I'm in a cube farm).
I can guarantee you no one on my team (of developers, of varying ages) knows what mind maps are, except our BA, who got handed one by someone on ANOTHER team.
Eczema. You're welcome.
Sorry -- I couldn't get past the opening line: "She is hot!"
Ok, now I know the crew. Thanks, Datamation article, we'll call you!
My JRE wants to update itself every time I turn around, and I say "why, yes, go ahead". Where does this "quarterly update cycle" statement come from?
"Modern"? That plant was built in the 60s.
I wish. Split tickets = split government.
Right. Except THIS is the stuff that matters, not real-time cloth texturing.
It's not management. It's not lack of financial incentive. Mgmt doesn't have time/energy to scrutinize docs, and paying for docs is stupid because you'll get filler.
It's thought leaders on the team. You get some architect who wrote the system and fully understands it, PLUS he's smart, PLUS he's a git r done type (remember? remember? smart, gets things done? Thank you, Joel Spolsky). Result: the smart guy everybody looks to writes no docs. He doesn't need them. It doesn't occur to him that others might need docs, because it's not an immediate problem (fire, crisis) he can put out and be a hero. It's friction. No payoff for him to eliminate _that_.
So, everybody on the team follows his lead. There's no team culture of helping each other out by writing little love notes to each other that say such sweet things as "Returns the two highest priority items that are neither red nor flibbertygibbits (<see cref="isFlibbertyGibbit()"/>)."
All work and no play makes Jack a dull boy. blah blah blah
Hey, is this enough comment to pass the filter that says I have to say something more than what I can squeeze into the subject line?
Great Scott, how did I get logged out?
What I said was: No, the sad thing is there are people who think it's laudable to score humor points by stylishly saying they don't care and neither should anyone else.
tl;dr (yet)
But I do have something to say about the immediate response of "QA". These are design issues (as has been mentioned). QA is not where you test out that sort of thing. Up-front design (not necessarily Big) should be the first response. Now is not the time to slack off on design, just because a lot of the components have already been written.
Development is also a cost center. Those whiners are constantly bitching about architecture. That's why we look for cheap developers who won't raise objections or otherwise make waves (like, with bright ideas), they'll just code. It's just a simple matter of programming, what the heck is up with them, anyway?
You're an idiot. I know some people who do exactly that.
How about if I raise hogs next to YOUR suburban house?
He's not a troll. If you search on "hackingbear" you can see that he's (probably) just some Chinese adolescent who's fallen for the nationalist line that problems in the U.S. mean China is no worse off.
Anthony Wiener's shens ==> it's ok to lock up dissidents in China. QED.
Sweet! I'm in!
MS is lying and you're a chump. (Sorry.)
(1) Both IE and the Bing toolbar are from MS. Doesn't matter whether they use one or the other; the directive at MS has come down from on high: use Google's results.
(2) The Google search results are only one input into MS's algorithm (they shouldn't be an input /at all/.) Of course all 100 honeypots won't show up. The fact that any did at all is incriminating, given that the data is completely synthetic.
I understand the technologies for both of those things have been lost. (Apparently, the Romans had some trick they did with oxhairs or sinews or something that gave their ballistas a lot more power than the competition.)
...and I have this to say:
Oh, bullshit.
[with feeling]
To know the difference between a million and a billion. Maybe a semester-long project to fill a swimming pool with a bucket?