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
"Document keeps formatting. Tried to go on different machines but still not working"
Where is the document? What program is the document for? Filename? Purpose? Anything? Nothing.... as well as obviously not knowing what 'formatting' means, as neither the computer-sense nor the page-laying-sense fit there.
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!
Fortune 25 contractor promises another Fortune 25 client that they can migrate their entire operation without a single desktop engineer. This was a 140 million dollar contract. Client also promised that their network conversion from 10Mb hubs to 100Mb switches would be finished before we started and then postponed the network conversion.
When everything was said and done lawyers for both companies mutually decided that I was the best the person on the ground with the best insight into why things fell apart. I was told by lawyers on both sides I would be subpoenaed as the primary witness and that the trial was expected to take about four months. I wasn't being blamed by either side, I was just the one who knew what the hell was going on.
When you testify as a witness (vs expert witness) you are limited to a $50 court fee and can't be otherwise reimbursed. I would have been financially ruined for other peoples idiocy and figured out a perfectly honest way to get out of situation their idiocy created.
I told lawyers for both sides that I would appear and testify, and they would neither one like what I had to say. They settled two days later.
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
...and they'll just make a better idiot. Two gems I've gotten over the years are:
"I can't log in when I type in my password! It's broken!" - The problem? They weren't typing in their username, they were only typing in their password.
My all time favorite was a customer who was very unhappy with an application we had created for them to send out event invitations and what not. I get an angry e-mail passed to me. The claim: "Whenever I type in someone's e-mail address, instead of e-mailing that person, the system figures out who their spouses and children are, and sends them the notification instead!" I had to repeatedly confirm that what they're describing is not possible. Even then, the person still angrily refused to believe me. If I were to create software that somehow psychically figure out all of that information, I'd be very rich, and probably be working for the government.
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.
users who don't know anything aren't the problem - users who don't know anything but think they know everything are the problem ...
It ain't what they call you. It's what you answer to. http://mylyceum.us/
I actually slogged through reading the whole Original Article and it seems like the editors at CIO don't know the difference between USER incompetence and incompetence in the IT department. Most of the "USER" issues were issues with the IT group, others were systematic failures... I particularly like the one where "IT" comes in and saves the day when "IT" diff's a developers' files and finds he's a bad developer, whereas the whole software Engineering department couldn't figure it out... yeah, right.
I think a NAT lease is when your home router boots up.
Are you kidding? That router is mine. I paid for it. Mine.
Faster! Faster! Faster would be better!
I have a bunch of those from that era - here's a couple:
User is used to Word Perfect, but has to use WordStar. User wants to print, so presses Control-P. Wordstar erases (p = purge in WordStar, print in Word Perfect) the document and the user hadn't saved it first. There was no confirmation dialog back then, either. An hour of typing a news article gone in a second.
User on a mac using Microsoft Word chooses Revert, but didn't know Revert means go back to the last saved version of the document and loses 2 hours of work. Note: Microsoft changed this from something like "Revert the document?" to "Are you sure you want to revert to the previously saved version" in the next version of Word probably due to a lot of user error and tears.
Unrelated to those, but related to TFA - when I was in college I heard one of the labbies (technically computer lab teaching assistants) was fired and kicked out of school but not details. I was friends with his roommate, so I ask what happened and found out he had been running a million+ dollar a year porn site off of the University servers (and this is the relatively early days of the public internet). If I had any doubts to the truth of it, they were alleviated a few days later when we all had to sign a code of conduct waiver, which included running sites of pornographic nature...
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!
Okay, serious question. Is it really a bad idea to make people's email addresses public? the article makes it seem like this is a bad practice. To me, if you are counting on email addresses to be private, that you have some crappy security going on.
""We took the roster of employees of our two largest offices and checked their corporate email addresses to see which were accessible off the Web. Out of 178 employees, 138 corporate email addresses were easily discovered -- like two or three clicks off Google. That alone surprised me."
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
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.
Only distantly related, but ... A long time ago I was writing code on a Perq workstation. The editor had a nice feature - it maintained a transcript of every change, and you could replay it. This became very useful once when I was working madly under deadline, and failed to save the file for ... wait for it ... 36 hours (yes, it was an all-nighter and then some). And the machine crashed - actually I think the power got cut. But with the transcript feature I was able to replay the entire 36 hour editing session, watching myself do my editing. It was rather fun, actually. Of course it was much faster than the original - I think it took an hour or so. And I was redeemed from my stupidity.
I loved the transcript feature - it was useful any time the machine or the program crashed, as it could restore everything up to the last disk write that succeeded. You could also pause and continue, so if you went off on a dead-end, you could replay up to the point where you started going the wrong way and stop, step backwards or forwards to the point where you had something worth keeping, and then save or start editing at that point.
I think it would be great for any text editor to do this.
It's easier to be a result of the past, but more fun to be a cause of the future! http://www.spacefinancegroup.com/
Holy fucking shit! I have had issues but nothing like that!
Just today, one of our remote sites was having an issue with an external drive that was causing an issue with a database. Such things are routine and our OPS staff normally handles them without issues. However the problem reappeared and the person who worked on it had already left. The new guy working on it sent a polite but utterly clueless email about it. The client of course exploded. I stepped in and said I would handle it. I have been here a long time and have a reputation of being competent and nice (or at least not being an asshole). You wouldn't believe how fast that email defused everything.
The bottom line is, karma is not just a ./ concept. If you build up your real-life karma by being reasonably good and not an asshole, you would be amazed at how much easier your life is
"Be grateful for what you have. You may never know when you may lose it."