- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
I'm surprised that this one didn't have a "John sat his desk being paid to do nothing" or "John then fired up Word" ending.
Admin
Admin
In a perfect world, employees would be rewarded for creativity and taking initiative.
In practice, even in a perfect world, there are two big problems with this.
Sometimes, often, doing something the same way everybody else does it is better than doing it your own way, even if you are convinced that "your way" is better. Even if your way is objectively better by any reasonable standard.
Of course this can go wrong if the organization gets stuck in the mud and refuses to consider new and better ideas. But sometimes a better idea isn't ENOUGH better to be worth the trouble.
Of course that process is far from perfect. Sometimes people are given authority because they are good talkers even though they know nothing, and they screw things up right and left. Many people who are quite competent are never given the authority they should have and become frustrated that their ideas are always ignored. Etc.
So I don't think the problem is that people generally follow the rules. The problem is when the higher ups are unwilling to consider the possibility that the rules are poorly conceived or out-of-date, or that there are times when there should be exceptions.
Admin
In theory... Sometimes you need to deploy a data-source definition where the name of the database-instance changes between environments. Or your Log4J needs to have debug-logging enabled in dev, but never in production. Or your a new database-table needs to use different tablespaces.
You can try to automate it as much as possible by using templates for configuration-files and some clever scripting that creates the actual files as part of the installation, but sometimes stuff goes past unnoticed.
Admin
And by the way:
If you follow the rules, and things go badly, it's not your fault, it's the fault of the person who made up the rules.
If you break the rules, and things go badly, then it's your fault.
If you break the rules, and things go well, you may still get in trouble for breaking the rules.
So from the employee's point of view, the safe thing to do is always to follow the rules.
Clearly the best strategy from a game theory point of view is to follow the rules.
Admin
Admin
From the article:
I'm not sure if this has ever been covered here, but the above statement basically describes what happened to Knight Capital last year. The orders originated from a test system and thus they had no risk limits in place. They were sent to the New York Stock Exchange and they couldn't just be cancelled. Knight had to trade out of them. They lost over $400 million in about 40 minutes, mainly because nobody could figure out how to shut it off. It ranks up there with Therac-25 as one of the biggest software WTFs ever.
Admin
Came here to say these things.
Glad I'm not alone.
Admin
Or the install team copied the web.config when they shouldn't have...etc., etc., etc.
There's reasons these things happen that have nothing to do with the code...
Admin
Configuration management fail, then, whatever. It's still bollocks. These are things which should never happen. If it does, that means someone has fucked up big time. No excuses for shit like this.
Admin
Admin
Actually, the best strategy is to try and become the person who makes the rules.
Admin
I want to work at a place where cake falls from the ceiling!
Admin
Where's the wooden table backdrop? This is not a high quality image.
Admin
Ha, only if.... When I worked at Fortune 500 IT, we have a team of app owners who refuses to follow any of the IT procedures we're told we must follow. Oh, they love to slam last minute changes on Friday afternoons at 4:50, thinking that all the IT "process people" have gone home, so they can try to bully you into breaking procedure. If that fails, they put our names to the C-level execs and threaten termination. So it's more like...
That's why I don't work there anymore.
Admin
(mistaken comment in here that I can't delete)
Admin
They used to say that about the school curriculum when I was in school. It wasn't true then, either.
Admin
Where's the WTF? Isn't this "all systems normal" in most organizations?
Admin
One of the biggest problems in IT is that people in positions with "manager" in the title (ie not just actual managers, but also release managers, change managers, incident managers etc) are very often non technical (or barely technical). Of course, we propeller heads quickly identify this issue and blame piss-poor non-technical people - but the problem is partially us. None of us want those boring positions. None of us want to be pen pushers, we thrive too much on the thrill of bug-hunting and the joy of seeing something we've written actually work. <cliche>It's a catch 22 and there is no silver bullet</cliche>. It is f'ed until people in management like roles actually understand what their role is and what they're supposed to be doing. At the same time, many of those who actually understand the role of these different positions (and understand that process has to be flexible to accomodate quick deployment of simple but critical changes as much as more considered deployment of complex, potentially high impact changes) are usually the people at the coalface making the change. I have worked for and with several TLAs (Three Letter Acronymns) who between dodging blame and saving money seem to have a layer of managers who's ability to handball would seem them star in any Aussie Rules team. These are the people who come to Post Incident Review meetings ready to fire with answers like: "I'm afraid I don't have that information, but I'll be sure to pass on your concerns to the technicians" or "I haven't got that detail on hand, but I'm expecting a summary of some totally unrelated data from our technical guys".
Perhaps the problem is the concpet of blame. With work often contracted out to the lowest bidder any issue becomes a game of dodgeball rather than any attempt to remedy (and God-forbid prevent) any issues identified. Rather than the idea of actually supporting a clients systems, the focus seems to be on avoiding any SLA breaches. Anyway, I'm getting too ranty....
steps off soapbox
Admin
Admin
TRWTF: QA, UAT, and performance tests passed... He checked in the code. Really? Finish all of your 'testing' processes, THEN check in the code?
Or maybe that should read "He deployed the release to production", in which case TRWTF is why the developer has any role to play at that stage anyway - these guys are big enough to have a separate QA section but the developers are doing the production releases?
Admin
TRWTF is that anyone would blame the code in the first place. By the sounds of things they have a whole pile of QA and approvals that must take place before something is put into production, so I would assume code review is part of this.
If someone "must" be blamed, then its a senior person's fault for not ensuring the process was followed or for not ensuring that the process can actually pick up errors.
Admin
All that, and no one mentions the dumb-as-rocks sysadmin who says "No need to roll back, we'll just tweak the settings?"
Seriously? If one of my applications went tango-uniform, and the sysadmin said that to me, I'd knock him in to next week and kick his ass on Tuesday. There's a reason my deployment instructions include rollback instructions: so that if the deployment is @&#^ed for a cocked hat, you can ROLL IT BACK.
That's TRWTF, right there. CM mistakes happen, young turk developers screw up, managers push too hard to make an unrealistic schedule ("We have to do it quick, we don't have time to do it right.") But when you're in a bad state, you back out of it. You can't "tweak" your way out of a train wreck.
Admin
Admin
Admin
TRWTF is they don't have an "offshore" guy from India, who could be blamed for their screwup.
Admin
What? Seriously? When did the BBC take over US education?
Admin
Admin
See Dumbing Us Down, a treatise by a New York teacher of the year on how this is exactly what's happening.
If you really want to understand why the US is falling behind its historical pace, it's because our school systems no longer teach independence, critical thought, or anything that might be useful outside of working a 9-5 and staying firmly entrenched in the middle class.
Admin
Can't have your own guns -> Can't have your own children -> Can't have your own brains.
Now citizen, get in this giant test tube thing full of breathable liquid so we can plug your brain into our parallel distributed processor, and simulate more war games.
Admin
Because they need just enough middle class to fund welfare, but not too much because the poor need to outweigh them in votes.
The rich, they're 1%, so their votes don't count. We give them just enough tax breaks so they don't pay off lobbies.
Rich tax income is fixed, poor tax income is negative. The middle class is the only place where we can continually raise taxes.
Admin
Holy shit, she's got like... $40 or $50 there! Now she can go out and get whore ink on her lower back!
Admin
Forget the wooden table! Where's the skin-tight t-shirt and provocative pose?
Admin
She's a wannabe politician in making. This is posturing at best, canvassing at worst. R.I.P Hugo Chavez!
Admin
Admin
I'm guessing that when you're at the furnace shoveling coal, you get coalface.
Admin
Admin
Aww, from the title I was hoping the story would be about a program barely alive. We can rebuild it. We have the technology. We can make it better than it was. Better. Stronger. Faster.
Admin
It's from mining. The coalface is the edge of the coal seam -- the part actively being mined. So to be at the coalface would mean you're working right at the deepest part of the mine doing the real work...kinda similar to saying "on the front lines".
Admin
Only in a closed system.
Admin
"You can't tweak your way out of a train wreck?"
Hot damn. That's brillant! It should be on a T-Shirt somewhere!
(I miss Irish Girl.)
Admin
Admin
I'm shocked that a WTF should turn out be a fuck up of some kind. How insightful of you.
Captcha is "nobis"...
Admin
SWIFT Interview questions on
http://testwithus.blogspot.in/p/swift.htm
For selenium solution visit http://testwithus.blogspot.in/p/blog-page.html
QTP Interview Questions. http://testwithus.blogspot.in/p/qtp-questions.html
Admin
Oooh, politics on a tech story forum.
"Smoke 'em up, Johnny! Cancer just tickles a little. And don't forget to beat the crap out of anyone different from you on the school bus!"
Admin
That's not really critical thinking, it's a matter of "I don't want to get blamed" x 1000. They know that they take no blame from doing nothing and they might take blame from doing something. So they do nothing.
It's still pathetic, though.