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.

Free advice take it or leave it
A few days ago I completed my one year work anniversary(is that how it's said) at my first job. And this rant is basically stuff I learnt and stuff I wish someone had told me when I was starting out. Here goes:-

When you are starting out your first job you would be a fresh out of college and people around you in college are your friends where as people around you at work are colleagues. Your friends can like you, but you have to earn the respect of colleagues.

If you sit yo ass too long u will become fat(started going to the gym again).

Don't bother your seniors too much. they have their own shit to deal with.

Don't bring your personal shit to office I don't want to hear how cute your dog looked while it took a dump on your carpet.

Avoid the person who gossips.
It's a two way street.

Whatever you find amazing your boss may not you know coz you are a geek and your boss isn't.

Don't talk to people when they are coding.Yeah just don't.

Avoid "below the belt" humor you may look funny but you loose respect in the long run.

Keep upgrading yourself don't stop learning.

Admit stuff you don't know don't Bullshit.

To sum it up it's a game of respect, respect of knowledge,respect of skill and most of all respect of attitude.

So we had this girl working with us as a graphic designer, she has a great sense of humor and pretty much impossible to piss her off

So April 1st is considered "a fool's day" here, on March 31 i sent an official looking email to everyone ( minus the seniors ) in our office saying how she's kinda shy about having her birthday on April 1st and everyone should wish her so she wouldn't feel awkward about it

Needless to say her actual birthday is not in April

So when she came to office on 1st, everyone started wishing her and singing Happy Birthday, she spent whole day explaining to everyone that came to wish

It was awkward as hell and pretty hilarious 😂😂

I have a telephone headset with a "confusing" mute button. Sometimes it works normally, but quite often it will "double-toggle" (toggle twice as though I pressed it twice, which essentially has no effect) - so I'm either left muted or left un-muted, the same as before I pressed the button at all - so I have to press it again, sometimes several times, for it to actuary work.

While I'm at my desk, I have a visual indicator of mute status (a light that turns green for un-muted or red for muted), so I can easily tell if my mic is hot or not. My old headset had a nice audible beep reminder if I was muted, but the new headset? Nope, not-so-much.

I work from home, while my wife works at an office; so each morning she leaves, but I stay in the home office. I almost always see her off one way or another, usually doing or saying something funny as she heads out.

So, one day, I'm on a large conference call with a number of cross-team managers, and my wife is about to head out the door. With the meeting droning on in my headset, I was in the kitchen with her for a while helping finish clean up after breakfast and getting her ready to go.

She needed to pack an ice-pack for some reason, and for the random humor of it, I start screaming something to the effect of "GIMMIE YO ICE PACKS - GIMMIE ALLLL YO ICE PACKS - YEAH! YEAH! IMMA PUT MY BAAAAAAAAALLLLLS ON IT - WHOOOOOOOOO!"

During which time I am jumping around like a crazy person, including actually grabbing one of the ice packs, putting it down the front of my pants and screaming. Loudly.

It was after my own screaming I overheard more than one person yelling on the bridge line "YOU'RE NOT MUTED! YOU'RE NOT MUTED!"

I have seldom felt such raw, unadulterated panic.

I rushed back to my home office - yes, the green light is on my desk - my mic is hot. When I pressed mute at some point earlier in the call, it double-toggled, leaving me un-muted, and I never knew.

Even more embarrassing was the chat session I saw on my computer screen. It was from my manager (one of the managers on the call) - he had pinged me several times while I was in the kitchen.

It read something like:

hey, you there?
is that your phone
I think your phone isn't muted
mute
dude, mute
is that you?
MUTE!
did you just say balls?

A few years ago I started a profile on a social media app to share programming endeavors and humor.

After a year or so I became somewhat close with the ~20 subscribers out of my ~1000 that would always comment on my posts. We started a programming group chat and all hung out there, sharing stories, posting random pics, etc.

When I was interviewing with my current company, I shared all the details with the group and kept them up to date while they cheered me on and wished me luck. Once I got my offer everyone was ecstatic.

One friend in the chat remembered my company has an office in NYC, where they live, and asked if I could arrange a tour. I asked around and it seemed like it wouldn't work out, but just a few weeks later I was sent to the NYC office to collaborate with another team for a few weeks.
I let my friend know I would be in town, and when the time came - we met up, toured the NYC office, ate really good tacos, and enjoyed the city.

10/10 would friend again.

what happens when you leave the office for more then a day.

Office humor, sorry its in dutch.

Frustrated that my build system wasn't recognizing a file change I added to my code. It kept telling me that a function didn't exist in the linked object (linker error). I checked everything and stared at this shit for about 15 minutes or more. The signature matched, the function existed, the relevant source files existed. I was starting to imagine impossible scenarios. I cleaned the project and recompiled. No errors, everything linked just fine. Fuck you? I guess...

So I decided to needed to walk around so I went into my bosses office.

me: I don't want to program anymore.
boss: What do you want to do?
me: Shovel shit.
boss: They are the same thing.
me: True...

TLDR: Tool and possibly skill issue results in frustration and humor.

!rant

So this happened sometimes ago.
We ,primarily, makes accounting software with industry specific integrations of manufacturing,etc. A soon-to-be new client visited our office for a meeting and a quick demo.
He's not satisfied with his current software and wants to switch but keeps bragging about how his current software operates and it's easier for him.(Only because he's been using it for years.)

NC : We used to do like that. Blahblahblah.

My Boss : Well, I built this new office last year. I visited "Taj Mahal" just before that. It was so beautiful. But it doesn't mean I should build a "Taj Mahal" for my office because it's not practical. Same goes for this software.

The client has a great sense if humor. He burst into laughing after 5 secs of silence. Not a single word of his current "system" after that.

PS : My first post.

Once upon a time in the exciting world of web development, there was a talented yet somewhat clumsy web developer named Emily. Emily had a natural flair for coding and a deep passion for creating innovative websites. But, alas, there was a small caveat—Emily also had a knack for occasional mishaps.

One sunny morning, Emily arrived at the office feeling refreshed and ready to tackle a brand new project. The task at hand involved making some updates to a live website's database. Now, databases were like the brains of websites, storing all the precious information that kept them running smoothly. It was a delicate dance of tables, rows, and columns that demanded utmost care.

Determined to work efficiently, Emily delved headfirst into the project, fueled by a potent blend of coffee and enthusiasm. Fingers danced across the keyboard as lines of code flowed onto the screen like a digital symphony. Everything seemed to be going splendidly until...

Click

With an absentminded flick of the wrist, Emily unintentionally triggered a command that sent shivers down the spines of seasoned developers everywhere: DROP DATABASE production;.

A heavy silence fell over the office as the gravity of the situation dawned upon Emily. In the blink of an eye, the production database, containing all the valuable data of the live website, had been deleted. Panic began to bubble up, but instead of succumbing to despair, Emily's face contorted into a peculiar mix of terror and determination.

"Code red! Database emergency!" Emily exclaimed, wildly waving their arms as colleagues rushed to the scene. The office quickly transformed into a bustling hive of activity, with developers scrambling to find a solution.

Sarah, the leader of the IT team and a cool-headed veteran, stepped forward. She observed the chaos and immediately grasped the severity of the situation. A wry smile tugged at the corners of her mouth.

"Alright, folks, let's turn this catastrophe into a triumph!" Sarah declared, rallying the team around Emily. They formed a circle, with Emily now sporting an eye-catching pink cowboy hat—an eccentric colleague's lucky charm.

With newfound confidence akin to that of a comedic hero, Emily embraced their role and began spouting jokes, puns, and amusing anecdotes. Tension in the room slowly dissipated as the team realized that panicking wouldn't fix the issue.

Meanwhile, Sarah sprang into action, devising a plan to recover the lost database. They set up backup systems, executed data retrieval scripts, and even delved into the realm of advanced programming techniques that could be described as a hint of magic. The team worked tirelessly, fueled by both caffeine and the contagious laughter that filled the air.

As the hours ticked by, the team managed to reconstruct the production database, salvaging nearly all of the lost data. It was a small victory, but a victory nonetheless. And in the end, the mishap transformed into a wellspring of inside jokes and memes that permeated the office.

From that day forward, Emily became known as the "Database Destroyer," a moniker forever etched into the annals of office lore. Yet, what could have been a disastrous event instead became a moment of unity and resilience. The incident served as a reminder that mistakes are inevitable and that the best way to tackle them is with humor and teamwork.

And so, armed with a touch of silliness and an abundance of determination, Emily continued their journey in web development, spreading laughter and code throughout the digital realm.