So we get in a Netbackup "drive down" ticket.
The new guy asks how to handle it. I pass him the fairly substantial document (~20 pages), and say very clearly "When you get to the robtest part, DO NOT STAY IN IT. You'll screw up the system if you do."
An hour later, we get an alert that the system can't control the robotic drives.
Genius McFuckstick started robtest, couldn't figure out how to run it, and then went on to work on something else without quitting. His login session timed out and he can't quit now.
There's a LARGE TEXT BOLD LINE saying not to do this.
I told him MYSELF not to do this.
He bloody well did it anyways.
This is driving me insane.
I had to wake up the damned Netbackup oncall to verify that we can clear this situation by killing robtest. For all I knew that would permalock the SCSI device, so I couldn't just go ahead and kill it anyways.
July 18 2005, 00:22:32 UTC 6 years ago
July 18 2005, 01:38:32 UTC 6 years ago
In theory, he's a trained UNIX sysadmin.
However, he has no analytical skills, can't multitask worth shit, and nothing sinks in until he does it a half dozen times.
I'm beginning to suspect that the entire reason he's now on our team, rather than the very high profile team he was on before, is because he's not capable.
Their team: brand new hardware, 19" LCD's on every desk, top-end dual processor desktops, proper cubicles, regular work hours.
Our team: older hardware, 17" CRT's, old generation laptops, shared workstations, and 7x24 12 hour shifts.
Me, I love this team because of what we work with. For me, I don't care about the equipment because it's what I've always had here. He complains all the time about how much better it was on the last project. There's no way he's here voluntarily.
July 18 2005, 01:44:05 UTC 6 years ago
Instead, I'm training him on the BASICS of these technology areas.
At this rate, I'm almost ready to welcome a strike because I'll be able to work solo again.
July 18 2005, 01:37:06 UTC 6 years ago
:)
July 18 2005, 11:18:16 UTC 6 years ago