I’ve had a good amount of incompetent co-workers in the past. One that stands out was this junior developer who worked at one of my previous companies. He was incompetent, but that wasn’t even his worst attribute. He was incompetent, and worse, he had a piss-poor attitude.

Myself and a few other devs at the company tried to help him, but he would literally get mad when people tried to help him. Sometimes he would even call one of us over and start getting snarky with us as we tried to help him. He was a piece of shit and a shitty developer. I don’t think he built one complete feature or fixed one bug in the year he was at the company before he was eventually fired.

Oh, and aside from his incompetence and shitty attitude, he had no sense of humor. It was so annoying. My friend and I made a little song based on his name and a group that sounded like his name, and he got pissed. We always used to sing it anyway after that and it always riled him up. I feel a bit bad about that now but he pretty much got mad at everything so whatever.

One of my favorite memories of him is when he was leaving one day, my good friend/co-worker and I were having a Nerf gun battle. The junior was leaving the office, and my friend tried to get him involved in the battle and shot him, but accidentally hit him in the back of the head. He said nothing, didn’t turn around, and just walked out lol. He was not happy about it.

I once had a co-worker (QA guy) who had the worst smelling breath of anyone's I ever smelled. He was a nice guy but it was kind of weird/irritating how bad it smelled. One day someone confronted him about it, and he said that it was garlic since he apparently constantly chewed on garlic. I guess it was just some odd habit and he didn't care he was grossing everyone out haha.

#3 Worst thing I've seen a co-worker do?

A 20-something dev, 'A', back in the early days of twitter+facebook would post all his extracurricular activities (drinking, partying, normal young-buck stuff). The dev mgr, 'J', at the time took offense because he felt 'A' was making the company look bad, so 'A' had a target on his back. Nothing 'A' did was good enough and, for example, 'J' had the source control czars review 'A's code to 'review' (aka = find anything wrong). Not sorting the 'using' statements, and extra line after the closing }, petty things like that. For those curious, orders followed+carried out by+led by 'T' in my previous rant.

As time went on and 'T' finding more and more 'wrong' with A's code, 'J' put A on disciplinary probation. 'A' had 90 days to turn himself around, or else.

A bright spot was 'A' was working on a Delphi -> C# conversion, so a lot of the code would be green-field development and by simply following the "standards", 'A' would be fine...so he thought.

About 2 weeks into the probation, 'A' was called into the J's office and berated because the conversion project was behind schedule, and if he didn't get the project back on track, 'A' wouldn't make it 30 days. I sat behind 'A' and he unloaded on me.
<'A' slams his phone on his desk>
Me: "Whoa...whats up?"
A: "Dude, I fucking hate this place, did you hear what they did?"
<I said no, then I think we spent an hour talking about it>
Me: "That all sucks. Don't worry about the code. Nobody cares what T thinks. Its not even your fault the project is behind, the DBAs are tasked with upgrades and it's not like anyone is waiting on you. It'll get done when it's done. Sounds like a witch hunt, what did you do? Be honest."
A: "Well, um...I kinda called out J, T, and those other assholes on facebook. I was drunk, pissed, and ...well...here we are."
Me: "Geez, what a bunch of whiney snowflakes. Keep your head down and you'll get thru it, or don't. Its not like you couldn't find another job tomorrow."
A: "This is my first job out of college and I don't want to disappoint my dad by quitting. I don't even know what I'm supposed to be doing. All J told me was to get better. What the fuk does that even mean?"
Me: "He didn't give you any goals? Crap, for someone who is a stickler for the rules, that's low, even for J."

Fast forward 2 weeks, I was attending MS TechEd and I was with another dev mgr, R.

R: "Did you hear? We had to let 'A' go today."
Me: "What the hell? Why?"
R: "He couldn't cut it, so we had to let him go."
Me: "Cut what? What did he do, specifically?"
R: "I don't know, 'A' was on probation, I guess he didn't meet the goals."
Me: "You guess? We fire a developer working on a major upgrade and you guess? What were these so-called goals?"
R: "Whoa...you're getting a little fire up. I don't know, maybe not adhering to coding standards, not meeting deadlines?"
Me: "OMG...we fire people for not forming code? Are you serious!?"
R: "Oh...yea...that does sound odd when you put it that way. I wish I'd talk to you before we left on this trip"
Me: "What?! You knew they were firing him *before* we left? How long did you know this was happening?"
R: "Honestly, for a while. 'A' really wasn't a team player."
Me: "That's dirty, the whole thing is dirty. We've done some shitty things to people, but this is low, even for J. The probation process is meant to improve, not be used as a witch hunt. I don't like that you stood around and let it happen. You know better."
R: "Yea, you're right, but doesn't change anything. J wanted to do it while most of us were at the conference in case 'A' caused a scene."
Me: "THAT MAKES IT WORSE! 'A' was blindsided and you knew it. He had no one there that could defend him or anything."
R: "Crap, crap, crap...oh crap...jeez...J had this planned all along...crap....there is nothing I can do no...its too late."
Me: "Yes there is. If 'A' comes to you for a letter of recommendation, you write one. If someone calls for reference, you give him a good one."
R: "Yea..yea...crap...I feel like shit...I need to go back to the room and lie down."

As the sun sets, it rises again. Within a couple of weeks, 'A' had another job at a local university. Within a year, he was the department manager, and now he is a vice president (last time I checked) of a college in Kansas City, MO.

#2 Worst thing I've seen a co-worker do?

Back before we utilized stored procedures (and had an official/credentialed DBA), we used embedded/in-line SQL to fetch data from the database.

var sql = @"Select
FieldsToSelect
From
dbo.Whatever
Where
Id = @ID"

In attempts to fix database performance issues, a developer, T, started putting all the SQL on one line of code (some sql was formatted on 10+ lines to make it readable and easily copy+paste-able with SSMS)
var sql = "Select ... From...Where...etc";

His justification was putting all the SQL on one line make the code run faster.
T: "Fewer lines of code runs faster, everyone knows that."

Mgmt bought it.

This process took him a few months to complete.

When none of the effort proved to increase performance, T blamed the in-house developed ORM we were using (I wrote it, it was a simple wrapper around ADO.Net with extension methods for creating/setting parameters)

T: "Adding extra layers causes performance problems, everyone knows that."

Mgmt bought it again.

Removing the ORM, again took several months to complete.

By this time, we hired a real DBA and his focus was removing all the in-line SQL to use stored procedures, creating optimization plans, etc (stuff a real DBA does).

In the planning meetings (I was not apart of), T was selected to lead because of his coding optimization skills.
DBA: "I've been reviewing the execution plans, are all the SQL code on one line? What a mess. That has to be worst thing I ever saw."
T: "Yes, the previous developer, PaperTrail, is incompetent. If the code was written correctly the first time using stored procedures, or even formatted so people could read it, we wouldn't have all these performance problems."

DBA didn't know me (yet) and I didn't know about T's shenanigans (aka = lies) until nearly all the database perf issues were resolved and T received a recognition award for all his hard work (which also equaled a nice raise).

A previous co-worker (dev) bought a "foot mouse" he found on a Chinese website, then changed his keyboard's layout to match the "natural human cognitive ability" also bought a sleeping bag because he needed a "power nap" after lunch break he even asked our MD to buy him an ergonomic chair which would cost around 1200 USD ( of course our MD refused) then the worst of the worst, he had this habit of chewing his food loudly when he's eating something he likes.
One time our operations manager (she was pregnant XD) screamed at him from her desk " RAYAAAAN SHUT YOUR FUCKING MOUTH I CAN HEAR IT FROM HERE DAMN IT"

He literally spilled some of the food he was chewing on his desk and I burst out laughing like crazy.
On the same day our MD told us to follow a new "no food in office" policy 😂😂😂

Sad story is that when he left the company I had to revert his PC to how it was including resetting the keyboard layout to default, remember his "foot mouse" ? Well he had to modify the mouse settings so all directions were inverted.

The first thing I said when I turned on his laptop was

FUCK YOU RAYAN!!

Worst fight I've had with a co-worker?

Had my share of 'disagreements', but one that seemed like it could have gone to blows was a developer, 'T', that tried to man-splain me how ADO.Net worked with SQLServer.

<T walks into our work area>
T: "Your solution is going to cause a lot of problems in SQLServer"
Me: "No, its not, your solution is worse. For performance, its better to use ADO.Net connection pooling."
T: "NO! Every single transaction is atomic! SQLServer will prioritize the operation thread, making the whole transaction faster than what you're trying to do."
<T goes on and on about threads, made up nonsense about priority queues, on and on>
Me: "No it won't, unless you change something in the connection string, ADO.Net will utilize connection pooling and use the same SPID, even if you explicitly call Close() on the connection. You are just wasting code thinking that works."

T walks over, stands over me (he's about 6.5", 300+ pounds), maybe 6 inches away

T: "I've been doing .net development for over 10 years. I know what I'm doing!"

I turn my chair to face him, look up, cross my arms.

Me: "I know I'm kinda new to this, but let me show you something ..."

<I threw together a C# console app, simple connect, get some data, close the connection>

Me: "I'll fire up SQLProfiler and we can see the actual connection SPID and when sql server closes the SPID....see....the connection to SQLServer is still has an active SPID after I called Close. When I exit the application, SQLServer will drop the SPD....tada...see?"
T: "Wha...what is that...SQLProfiler? Is that some kind of hacking tool? DBAs should know about that!"
Me: "It's part of the SQLServer client tools, its on everyone's machine, including yours."
T: "Doesn't prove a damn thing! I'm going to do my own experiment and prove my solution works."
Me: "Look forward to seeing what you come up with ... and you haven't been doing .net for 10 years. I was part of the team that reviewed your resume when you were hired. You're going to have to try that on someone else."

About 10 seconds later I hear him from across the room slam his keyboard on his desk.

100% sure he would have kicked my ass, but that day I let him know his bully tactics worked on some, but wouldn't work on me.

Worst thing I've seen a co-worker do?

Its all relative, I've seen a lot of "worst's". Here's one of many I'll try to post.

A (married) DBA would often come to work drunk, starting fooling around with a couple of devs (which we suspect she had sought adventures outside the IT dept based on rumors), and ultimately got fired because she was caught sleeping at her desk (and she was drunk). One of her conquests told us she came from a very poor childhood and this was her first real high paying job. Abusive husband, being attractive herself, and being surrounded by other attractive, highly intelligent, single bucks (aka horny) that had no morals, equaled bad decisions.

She wasn't the worst, it was the assholes who took advantage of the situation that makes it in my top 10 worst things I've seen.

THE WORST PRANK ATTEMPT

If i remember true, it was 2012. april fool day..

me and my co-worker (we were the founders) decided to fool our members (we had a script's unofficial support forum). so, we did the plan. we register another account on march and wrote a few useful messages with it. help guys with that fake account (named as Root).

on fool day, we move the site to hidden folder (but didnt backup it) and added an index file as "hi, i am Root. you know me who am i. i hacked this site and deleted all dbs. cya later" (in turkish of course)

and we sit our chairs, began the watch our messages from facebook,skype,whatsapp etc..

we act like we are in trouble and we cant solve the problem.
at the same time, one of the our crew, decided to help us :D
so, he contact with our server's management crew. they dont know the fool too :)

server management looked up the situation without try to contact with me or my co. and we got an email from server like that
"hello tilkibey and impack, we just realized your site is hacked. so we delete your all ftp and db for safety. please contact with us asap"

we shocked and contact with them, explain the truths and request the recover our site (because we though they backup site before deleting all things). but they didnt backup it :(

so, we recover our last backup which is got nearly 10 days ago :(

#4 Worst thing I've seen a co-worker do?

Not a direct co-worker, during a fire drill, a call center manger told all the agents to ignore the alarm and keep working.

My co-worker not only doesn't create unit tests, he comment out my own unit tests after he changes the code and the test breaks.

Nowhere near my worst co-worker, but still funny.

The Dev team were all in a separate glass walled room with the business & support staff out in a bigger room outside. As is our wont, we wore headphones while working a lot.

One of the non technical folks asked me why and I said it helps me focus by keeping out distracting noises.

"Oh, I thought you were listening to code or something"

😮

It was kind of an eye-opener as to how little clue a person sitting just 4 meters away had of what I did or how I did it. And actually it helped explain some confusing interactions...

It was my internship and I've end up working on a law company specializing on Australian construction laws they're working on a website that will take care of all the paperworks for the contractors. They have a dev team who's working on it but they don't have a web designer. I was accepted for the job as an intern/web designer/tester. I was so happy that I've got a really cool internship as a designer but that's only for a second.

The hell starts on day one. They've told me that they're using agile workflow and that they need to make the website responsive. It was based on bootstrap and gosh their code was so broken. HTML tags overlay on each other, some are unclosed. I've tried to fix the problems and did a great job at that. Made the front page responsive and all laid out. When I went to the next php file it has a different header.php and footer.php and same problems apply and we're not even touching the worst.

They didn't use any version management and they're cowboying everything. Now that the website is on the staging server they use Cpanel text editor to edit the code! My headache started to pileup.

The Australian client asked me to provide icons and fix the colors of the website. Also the typography looks great already. I've fixed almost all the problems and I'm satisfied with the design when suddenly a new co-worker from a famous and expensive college was absorbed by the company. He worked as the marketing specialist who has no experience at web design at all. He told me to do this and that and the whole website changed. He bullied me for my skills in design (I'm an intern) and just took over the whole design. Everyone even the boss listen to him as if everything he say is right. He's skilled at design but not web design. He made the website look like a freakin movie poster.

All my works are for nothing, I got headache for nothing and I've got hated for nothing.

It was the day when I finished my internship. It was a long 3 months. After a month I've heard from my co-interns that the whole dev team was fired including the marketing specialist. Also the whole website is scrapped and has been rebuilt by a single guy who used WordPress which he did in only a month.

For me, the worst co-worker is one who works by the principle of quantity over quality or a person who thinks quick and ugly fixes are a valid way to solve problems. Also: If there are unittest, don't fucking dare to change or remove them, just so your code runs without errors.

But in general, I just can't work with people who don't really think about what they are coding, people who just code straight ahead without making the simplest plan about how to solve something. Most of these people realize too late, that their approach was rather shitty, unreadable and unmaintainable.

I often see memes about "I forgot what I coded last [insert timespan here]". Though it is kind of normal, if it takes you too long to find out what you wrote, you should consider overthinking your coding approaches.

Just my 50 cents.

Damn I miss coding... 4 weeks of learning & exams is too long...

Oh look, you aren't doing shit. You have 2 weeks worth of testing to complete and you are checking out stories on the Yahoo front page.

Useless. Completely incompetent. Idiot. Imbecile. Moron. Stupid. How dense? Let me count the ways...

Do you know anything?! You use big words to sound important and look like you know your shit. In reality, you have no clue!

How you have managed to capture this job is baffling to me. It shows there is much work to be done to filter out toxic, incompetent people like you. Otherwise, the industry will be plagued with a terrible fear of sub-par employees.

Your lack of common decency for the office space is appalling. Your attitude and "can do no wrong" personality is disgusting. And the cherry on top? It is impossible for you to admit mistakes and take ownership for your actions. You can be inexperienced, stressed out, or even make a mistake once in a while. Yet, the moment you DO fuck up and act like nothing was your fault, that most of it was MY fault, or the TEST environment's fault, or the other team's fault, a lack of resources, a lack of time, ANYTHING but your own damn incompetence, you are dead to me.

You are, by far, the worst co-worker I have ever had.

A co-worker on a gigantic PR i made:

"the worst thing about this pr is that while i was reviewing it, I forgot about my coffee and it turned cold. Otherwise good job!"

Worst disturbance is co worker microwaving eggs for breakfast and then eating them at his desk.

One thing about microwaved eggs cause the egg smell to be intensified like 100x

Tomorrow, we will have a new fenale co-worker.
This is awesome, because in IT is very rare to find women. It seems that this field is dominated by man.

And that brings the problem. In our enterprise, we are all men. We worst kind of men. Saying that we are "a bunch of animals in a tiny room" would be more like a compliment.

I already feel sorry for her. :/

Today a co-worker (I am going to call him 'boss') ask to another co-worker (I am goin to call it 'useless piece of shit' or 'ups') to explain to me a new task, becaus boss was to bussy with a new release for a client.

Idk how but ups managed to explain all wrong, like terribly wrong.

Ups: "Dev, all you have to do is fix some queries from local files"

Dev: "Ok, seems legit"

Try the local files, nothing happend

Dev: "weird... ups why this is happening?"

Ups: "I know the same as you, ask boss."

Dev: "boss this."

Boss: "what the actual what? ... this is all wrong. The config file is in mongo, in this IP, we don't use local files anymore. I tell ups to explain this to you so I can atay focused on this other task, but now I lost the double amount of time"

Dev: "oh... sorry, I will fix the remote queries"

I hate ups, every fucking time soneone need something from him this happend or worst...

This is about both worst boss and most annoying co-worker.

Well, this boss didn't care how much code we wrote, or how good it was (well, at least he didn't care that much); only how much commits we do. And this coworker literally did a script to do a commit every 10 minutes. 24/7. Everyone else was completely mad about it and about a week later we achieved that he was kicked from the job. Since then I still get trauma if someone commits something unimportant.

The worst co worker I had is actually pretty recent. He joined a well integrated team on what was basically a legacy project. He sounded like a good developer and seemed to know his stuff but it took him ages to push out fixes/features. They were always massively over-engineered, poorly named, partially tested and what documentation he did write still managed to bitch about how poor the project was structured.

He spent most of his time bitching about the general shitty nature of the project (he wasn't wrong) and the lack of interest from other Devs.

He was so unpleasant in interpersonal communication that by the end no one would work with him.

In his last team meeting he basically said he was glad to be going and that we were all lazy, disinterested and shouldn't consider ourselves his peers. The equivalent of storming out of a party after setting the couch on fire and shitting in the sink.

We've since removed all his overcomplicated, not standard, unmaintainable code.

I guess I'm my worst co-worker because I'm self-employed 😁😂

This is a true story when I was working as a application technician a couple of years ago!

Before I started working there, they had a couple of incidents with ppl with less knowledge accidently deleted stuffs in prod databases, and only a handfull of ppl get the full access to them. I started working in this team, and one day I was asked to run a snippet in one of the prod databases from a co-worker with less privilege.

Loged in, run the snippet and the server STALLED for a couple of minutes! When the snippet was finished I looked at the screen and saw the output "1724217 rows deleted". The fun part here, was that we went to a coffee break right after this, and after a couple of minutes we started to hear ppl mumbling that the network was slow as f*ck, servers didn't respond etc etc.

Well, I responded that I got a snippet that deleted 1724217 row in a table and we ran back to our computers and started to work backwards to solve this.

The best part in this story is that:

* Was not my fault! Even thou I was the one that executed it.
* The tables was deleted from a live prod server that was not heavily used!
* I asked for a life line for us in this team, that we needed a prevented output so we can "match" the actual output after we ran it in prod from the ones from the developers!

Even thou it was not my fault, this is the worst mess up I have done working in IT over 10 years. O_o

Omg!!!. Its a Sunday. Not a Monday. No one else is here but the security guard. Why are all the fucking lights on when I walk into the office. Co worker says oh well is it okay if we leave the lights on for a bit......like why 🤔. Let me remind you. All my devices are in dark mode. This is the worst 😫.