Pilot fish gets a message from someone else in IT, telling fish to give Fred access to the Y: drive -- which isn't actually a very useful request.
"We have a lot of different sets of mapped drives, and no two are the same," says fish. "I find Fred and ask him where exactly he needs this Y: drive to go. He says he has no idea, but that he needs access to some schedule that Barney creates and uses."
So fish goes hunting for Barney to ask him where that file is so fish can create the Y: drive shortcut for Fred.
Turns out Barney isn't in, and it's already 15 minutes past when fish is supposed to leave. He asks Fred if this can be taken care of Monday. Sure, Fred says.
Fish emails Barney asking him about the schedule file and where it's located so he'll have the information on Monday to create the shortcut.
Then he leaves for the weekend.
On Monday morning, fish gets in expecting the information from Barney so he can create the Y: drive shortcut. But there's no email from him. OK, shrugs fish, maybe it's one of those requests that ends up not being needed.
"About two hours into the day, I get a reply from Barney with only one question: 'Is this done yet?'" fish reports.
"Over the next few emails it becomes clear that because he had talked to a different person in IT -- not even the same one who gave me the request initially -- he assumed that this was going to be fixed without anyone knowing where the Y: drive shortcut needed to go!"
Your story needs to go to Sharky. Send me your true tale of IT life at firstname.lastname@example.org. You'll score a sharp Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.
Get your daily dose of out-takes from the IT Theater of the Absurd delivered directly to your Inbox. Subscribe now to the Daily Shark Newsletter.