I did this three years ago. The company is going bankrupt now. Coincidence? Definitely.
this post was submitted on 31 Mar 2025
600 points (99.7% liked)
Programmer Humor
22156 readers
2521 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I did this recently. They "replaced" me with two engineers after I had been begging for meaningful help for months.
Well, that's maddening.
Why the quote marks?
Because as far as I know, they only finished the immediate project that I was working on and didn't continue doing any of the next things on the roadmap that were sorely needed. A fintech company that somehow assigned zero importance to their payments system.
Management works in mysterious ways 💫
Management is always managed by the Peter Principle.
Peter Principle
Is that your new CFO?
Oh shit, there might actually be a guy with that name.
Because our King can never be truly replaced. ✊
At 4:30 pm on my last day at my previous job my boss asked me to email a customer something.
I left that shit on read
Bonus points for having the "Read" timestamp 1 second before logoff.
I just know that for decades people will check the git blame and curse my name.
Protip: Add a minor inconvenience to every line, like a trailing space or slightly misaligned indentation. That way the next guy who opens the file will automatically correct it, taking the git blame.
My company had 2 types of people...
Everyone else: who used sometimes 3 or 4 spaces (yes, manually pressing the spacebar even though the IDE provided them);
Me:
Commit 1
Added .clang-format
Commit 2
Ran git clang-format
The feeling is even better when they let you go because you no longer have a moral obligation to transition anything over to your coworkers. You can just fuck off and not feel bad. This typically highlights all the holes in management when they are ineffective at delegating your tasks and things get dropped. My husband witnessed this happen recently. They let an employee go nearly a year ago, then a client started sending emails wondering what was happening to their project and why there hadn't been communication.
you no longer have a moral obligation to transition anything over to your coworkers.
My coworkers didn't let me go, my boss did. If i knew a shit coworker of mine would inherit the project then sure, otherwise i don't see the point of burning bridges.
I once worked at a place where I built out a bunch of internal tools that became pretty heavily integrated into the development workflow. Everything I built was the shittiest, most disgusting piece of garbage I've ever seen, but it worked. My job became solely managing these tools, as everyone else struggled to read and comprehend my filth.
I ended up switching jobs because they wouldn't give me the compensation I asked for and half of the development team quit before my 2 weeks was up to avoid dealing with my slop, a lot of them were already considering leaving for lack of compensation, but this was the nail in the coffin.
I found out a few months later that instead of just going back to life without these tools or finding someone to take them over they just shut down the development department. The people who were left either got fired or moved to a different department to pursue a new career path.
It’s the best feeling ever realising that you won’t ever have to deal with any of the tech debt again
Never Forget
I laughed out loud at this as i stare at a stalled process i couldnt give an inch of fuck about.
#include <memes/wow_this_is_literally_useless.txt>
Of course it’s dripping mysterious black juice.
At the tail end of my last job I was saddled with a massive project to migrate a client to a new version of an application. We did this by standing up the new version, copying over their current data, asking them to test it and then cutting over when they were ready. This was a huge undertaking because most clients had one or two environments but my client had 18 different environments so the workload was way higher and everything took way longer.
On top of the scope they also took updates to these environments almost every night which meant it was a full time job just to keep things in sync, setup a testing window and then try to get them to approve the new state of things.
I was already burnt out before this all started, but thanklessly maintaining 18 non-production environments by myself for an application that no one could commit to testing or cutting over was driving me insane. I felt such a weight lifted off my shoulders when I quit. It came at the end of months of stress and wasted effort. I couldn't imagine a reality where anyone else would put up with that work or have a better chance of success.
Anyway I caught up with some coworkers and asked if that project ever got done. Apparently it got passed to a small team of three to manage and after getting jerked around for months themselves the whole thing fell apart.
So glad I didn't waste any more energy on that shit.
Currently suffering through the pain of a programmer leaving a year ago and seemingly no one inherited his knowledge of the stuff he was working on for one of my projects. It was also the fault of other departments for delaying my work for even longer but they don't care. It's agony having to ask around the office for someone who might actually have the info I need.
I left my code in way too good a shape. Even documented. They didn't deserve this at all. :)
Why wait until you quit? I'll do that when we get a new guy?.
FNG gets passed the shit tasks I don't have time for 🤣
Currently going through this lol. React is pain in general, but React that I'VE written is a crime against humanity
That's how the ancient knowledge of the lab gets passed down. Well, ideally before you leave. Gotta teach the new generation.
Just did that 😅