Tales of IT Idiocy
snydeq writes "IT fight club, dirty dev data, meatball sandwiches — InfoWorld offers nine more tales of brain fail beyond belief. 'You'd think we'd run out of them, but technology simply hasn't advanced enough to take boneheaded users out of the daily equation that is the IT admin's life. Whether it's clueless users, evil admins, or just completely bad luck, Mr. Murphy has the IT department pinned in his sights — and there's no escaping the heartache, headaches, hassles, and hilarity of cluelessness run amok.'"
It's not really IT related, but in a similar vein to some of these stories, the worst workplace war I've ever seen erupted over a parking space. Here were two college-educated adults, both of whom made over $100,000 a year--at war with each other because one maintained that he had been assigned said space (even though it wasn't marked) and the other kept parking there. Combine that with weak leadership at the company, and bam!, you had an escalation that got fucking crazy. First it was potshots and pranks, then they started keying each others' cars. Then they were openly screaming at each other in the office. It only ended when the cops had to get involved (they were calling each other with death threats and one of them showed up to the other's house with a gun). They both ended up with restraining orders...and also pink slips (when management finally woke up and realized they were both nuts).
When you're in the city, people take their parking spaces VERY seriously. And little things can become very big (in your mind) if you obsess over them long enough.
But, hey, if the assassination of one dipshit Archduke could start a World War and one little fruit vendor setting himself on fire could start the Arab Spring, I guess any little thing can spark a fire.
SJW: Someone who has run out of real oppression, and has to fake it.
Anyone have a Greasemonkey script on-hand that automatically hides stories containing links to infoworld.com, or do I have to whip one up on my own?
The Daily WTF has a lot of fantastic stories about what not to do. The stories include horrific interviews, code that makes you want to squirm at best, and plenty of IT mistakes.
I am officially gone from
They'll have more tales of idiocy, and you won't feel like you need to take a shower afterwards. Seriously, InfoWorld, SIX pages? That's a WTF in itself.
Reading InfoWorld is about number 6 or so.
In my time I have seen some amazing examples of idiocy.
I once had to lecture some linux admins as to the nature of ntpd and how they don't have to be constantly logging in to set the time, but here's the brilliant part of that equation: someone had come up with a "login script" idea, that used ntpdate to set the time. So all they had to do was log in to the system and the time would be automatically set. I only got involved when they were trying to develop an automated login system so they wouldn't have to log in to 500+ linux servers, constantly, all to keep the time set. I actually had to argue with them, to show they what ntpd could do. It was unreal.
Then there was the time I found windows admins that thought you had to have a user account for every machine you joined to a domain. A unique user account. A unique administrative user account. And because they had several thousand machines, password maint was a nightmare...or at least would be, except they came to the conclusion that using an easy to remember password on all of these administrator accounts was an easier solution.
Mod me down with all of your hatred and your journey towards the dark side will be complete!
They were running an older CRM version that still used direct file access.
Because of this, their backup solution (for which they hadn't bought the live file backup module) would fail every night due to someone in the office leaving the program open.
So they "fixed" it.
6 months down the road they had a server crash and lost everything.
So we're like "Okay, let's roll to backups. There's still data loss, but minimal, a day or so."
Uh. What backups?
Their "fix" had consisted of simply deleting that CRM program's directory from the backups (see: NOT BACKING IT UP) so their backup reports were all nice and pretty.
The latest real backup this company had was over 6 months old.
The company that was in place to handle their IT was out on the curb with smoking ears and a boot-print on the ass shortly afterward.
Chas - The one, the only.
THANK GOD!!!
>only 10 submissions of fail in the TFA.
Someone already mentioned the Daily WTF, so I'll post its little brother.
Always an interesting read.
http://blogs.computerworld.com/sharky
--
BMO
We get a lot of fluff pieces on the front page of slashdot via Infoworld and I've always wondered what mechanism they are using to get such high returns. Do they have their employees vote up stories in the firehose, or are their articles genuinely interesting enough that they earn their place on the front page? If they are "gaming the system" somehow is that something that slashdot's staff should be policing?
I'm not trying to cry foul or call anyone out. I'm just curious about what drives some of the patterns that emerge on slashdot. If someone from either Infoworld or slashdot could weigh in that would be great.
it kind of is possible, many people have email accounts that direct to several mailboxes, like @familyname.com. If your app was sending to an unknown name at the front of that (instead of 'dave@family' it was 'whoever@family') then its possible it got delivered to all accounts using that shared mailbox system.
Not that I'm saying this is what happened, but something along those lines due to some wacky configuration.
Moral: never disbelieve the user, although what they say is impossible, when you look at it, you find that not only is it possible, it's also happening. If only we could get the users to describe it in terms a tech would understand.
IT idiocy? Is there a more idiotic tech site than IT World itself, with its twenty ad-laden pages for ten paragraphs, after a goddamned splash screen? I refuse to visit those morons. No RTFA this time, folks. Link to a respectable site next time.
Free Martian Whores!
"Never disbelieve the user" is right. One of my early tech support calls (many moons ago) was from a guy who claimed his computer rebooted every time he flushed his toilet.
Yeah. I figured he was yanking my chain, but you can't just hang up on people, so after humoring him for a few minutes we actually set up a tech visit.
We fixed him up, at least temporarily, by installing a UPS for his system.
He lived way out in the boonies and used well water and a septic tank. Turns out when he flushed, not only did his computer reboot, but his lights flickered for a moment, too. Flushing the toilet activated some power-hungry pump in his water system, and the draw was browning out his computer.
End of lesson. You may press the button.
One day a woman came in, worked on a paper for a couple of hours, and then had her computer crash. She went to the lab assistant on duty, who didn't try to be helpful or sympathetic at all -- he just blew her off with a "well, you should have saved".
She blew up at him. Yelled, screamed, made a gigantic fuss. Lab guy thought it was funny, still wasn't trying to calm her down or be helpful at all. The supervisor heard the noise (his office was across the hall from the lab) and came in to see what was wrong. He talked to the woman, got her to go across the hall where she wouldn't be disturbing everyone else who was still trying to use the lab. There, he offered sympathy, offered to help her with retyping.
Once she started to calm down, she started crying. He finally found out that she'd been raped a couple of weeks before. She'd lost a lot of time for getting ready for finals and doing final papers in doing interviews with the police and the prosecuting attorneys -- and then found out earlier that day that the DA's office had decided not to prosecute her attacker, because he was a former boyfriend of hers and they were afraid they wouldn't be able to persuade the jury that it wasn't just her changing her mind after the fact.
He pointed her to the campus rape center so she could get help -- not just with the legal case and the emotional fallout, but also to have them talk to her professors. She didn't need to be trying to handle finals like that.
The moral is: You don't know how bad a day someone else has had. When people get extremely upset over something that seems like it shouldn't be that upsetting, there's a good chance that they were already upset about something else. And, of course, he added that if we had someone in the lab we just couldn't handle, get him or call the campus police if it was after his office hours. We should try to be nice, but remember that our job was lab attendant, not social worker.