FNG finally gets fired, but goes out in the worst way he could have Tech Support |
| FNG finally gets fired, but goes out in the worst way he could have Posted: 01 Sep 2021 08:24 PM PDT Been lurking here for a few years, and while this story isn't really tech-support or anything like that, u/iammandalore's stories of his FNG made me want to post about the new guy we just recently lost due to him being inept, lazy, and/or just didn't care. Probably not the most entertaining story, but how could someone be this stupid? Background: I work for an IT contracting company, and the contract I'm on is as a Service Desk tech at a hospital. My boss works for the same company I do, and he reports to the hospital's CIO. After some schedule changes, somebody quit, more schedule changes, and new people were hired and trained. I got moved into M-F 2nd shift after having been on M-F 2nd shift then 3rd shift on weekends. This is about the guy who took the shitty hybrid schedule I just left. Well, mostly about the event that caused him to be fired. Prior to this final event, he rarely responded to any communication directed at him regardless of importance. There was one night we were working together where I had to go off-site to image some computers, and hadn't heard a word from him all shift. He wasn't answering calls, texts, messages in Webex, nothing. It took multiple calls from bosses to get him to acknowledge anything. When I did see him in person, he barely spoke a word to me unless he was on a call and needed help, which he needed. Frequently. Myself and other coworkers have had to coach him through some of the simplest things we do multiple times. He also regularly neglected the very few tasks he had on those night shifts, and I've gotten too many calls from users who were speaking with him and said that the call dropped suspiciously while he was working with them. Toward the end he seemed to be getting better, but man was he not at all. We all knew he was going to be fired at some point, but were just waiting for the when and why. This is the when and why that I've been told from my boss and a coworker. I heard this from my boss after I got up Monday morning, and this happened around midnight on Sunday night, during my now-former coworker's night shift. Found out later from another coworker that it was about an hour into his shift, as she was called in to take over at around 1AM. According to my boss, the And he was found. By a security guard and the on-duty nurse supervisor. When they confronted him, he got argumentative to the point where they had to call the police to escort him out of the building. Security took his badge, and then he had the testicular fortitude to sneak back in. When he was found again, they had to have the police escort him out a second time, and he was drunk. He might have been drunk the whole time, but I'm putting this together from multiple sources so who knows. That series of events over the course of an hour or so was the final straw, after many of his fuck ups. It wasn't my boss who fired him either. It was the hospital's CIO. At around 1AM on a Monday morning. Funny thing is that apparently when he was interviewed for the position, he did very well. In practice though, he was barely good enough to just answer phone calls. Found out after his first few fuck-ups that he was going through some really rough life stuff, causing me to think "why the hell would you do this when you need the job?" Whatever the reason, good riddance and thanks for the overtime. TLDR; now-former coworker already on his last chance gets drunk and argumentative to Security when caught sleeping, gets kicked out of the building twice, then fired by the CIO. [link] [comments]  |
| The New Guy Chronicles - Episode 3: Mr. Confident Posted: 01 Sep 2021 11:11 AM PDT These are the stories of the New Guy. All of what you are about to read is true. I write you these tales of mirth and woe, of entertainment and anger with as much accuracy and as little embellishment as I can manage. Many conversations are written as best I can remember them from my notes and memories about the incidents they describe, but the heart of what you are about to read is as true as I can make it. Names have been changed to protect the innocent. And the guilty. The cast:
DAY 10.2 - Mr. Confident Along with the fetid stench of betrayal, day 10 reeked with another more subtle odor: misplaced confidence. Jordan had stated - with the confidence that only ineptitude can supply - that he believed he'd done enough studying (read: watching youtube "training" videos) that he could build a computer. Smirking quietly to myself, I set out to test his theory. I found an old computer and monitor slated for disposal, and in a back room I ensured that it booted correctly. I then disassembled it, removing the RAM, video card, memory, CPU, power supply, disk drive, and hard drive. I gathered these parts and laid them out on our bench. Upon seeing the smorgasbord of circuitry, Jordan's interest was piqued. "What's all this?" "You said that you thought you could build a computer. Well, Mr. Confident, here you go. Put this one back together." He began the assembly, and straight away I could tell that failure was certain. During the process he required assistance getting the disk drive, PSU, and CPU/heatsink mounted. All of this help was provided only after he asked. Upon pressing the power button for the first time after "fully assembled", the angry pixies failed to chooch, and nothing happened. Minutes passed in silence before the inevitable happened. "I'm not sure why it won't turn on." "You forgot to plug in the power connectors for the motherboard and CPU." "Oh! OK." Attempt number two, alas, was to fare little better. This time the attempt produced a series of beeps, and again Jordan's befuddlement was clear to all spectators. "It's powering on, but it's not booting correctly." Harkening back to a conversation we'd had only a couple days prior, in which I'd explained beep codes and error lights commonly found on computers, I opted to give him only a slight nudge. "You have all the information you need to diagnose the problem." "Everything is plugged in I think," he said after a few minutes. "The computer is giving you all the information you need." Remeniscent of Red Leader in the trench run on the first Death Star, my hint again missed the mark and just impacted on the surface. "The beep codes, Jordan." "Oh, right." After looking up the beep code we discovered it was a memory error due to the RAM not being fully seated. Similarly, video output was garbled upon the next boot which we resolved by seating the video card fully. Next was the hard drive, plugged into an inactive SATA port. Finally, with everything properly in its place and seated, the moment of truth. Jordan, putting one foot in front of the other and confidently striding past his previous failures, pressed the power button for the final time. His giddiness at his imminent success was palpable. It would be short-lived. The machine would POST, surprisingly, but not boot. "I don't understand. Everything is installed correctly now, right?" "Yes. But you made a mistake earlier that makes it all irrelevant. Unplug it and remove the heatsink and CPU." He did as told, and the evidence of his crimes against machine-kind were laid bare. "You see that?" "Yeah... What is it?" "Those are bent pins smeared with thermal compound from when you tried to install the CPU upside-down." "Is there any way to fix it?" "No. Not unless you think you can scrub away all that thermal compound and bend those hundreds of pins back into the precise shape they should be in. You're lucky this computer is one we were throwing away anyway. It's ruined unless we want to just replace the motherboard." "Oh. Well at least I got most of it right." Ah. To live in such blissful ignorance of one's own incapacity. [link] [comments]  |
| You are subscribed to email updates from Tales From Tech Support. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment