Manager: THE SERVER IS DOWN THE SERVER IS DOWN!!!!

Dev: Ok I’ll look into it

*5 mins later

Dev: Wow these are really strange logs, it’s like config values are being changed all over the place while I’m looking at it

Manager: Well I figured while you were looking into it I’d go i to the server settings and change everything I could find in order to try and get the server back up again. Two sets of hands are better than one, Is it up yet???

Dev: …No.

Manager: I THOUGT YOU SAID YOU’D LOOK INTO THIS. I NEED ANSWERS NOW. WHAT IS TAKING SO LONG?!?!?

Dev: …

Manager: This code you wrote violates the single responsibility principle!!

Dev: How so?

Manager: You have one function that you call in *MULTIPLE* places. That’s too much responsibility for one function! Functions should only have one responsibility!! Creeping the scope of a function beyond that is a TERRIBLE way to write code!

Dev: But why spin up multiple functions that all perform the same thing?

Manager: Well if a function has a bug in it and you use that function multiple places then that bug exists everywhere you use that function. If a function only has one responsibility then if it has a bug that bug will only exist in the single place it is called! You really should think first before asking questions like that.

Dev: …

I fled russia

Fuck you, I Quit

"Why did you bring Wagyu beef to the meeting?"

"Because the calendar description said: Engineers should proactively add value for our steak holders"

(True story -- They told me to do what management instructs, without correcting anyone and without asking questions. And I love playing that game!)

Dev: So how do you want this feature fixed?

Manager: It should work how it worked before.

Dev: I'm new to this feature, I don't know how it worked before or what is broken about it.

Manager: Well just make it work like it worked before.

Dev: I DONT KNOW HOW IT WORKED BEFORE THAT IS WHY I AM ASKING YOU. PLEASE TELL ME SO I CAN DO MY JOB.

Manager: Just how it worked before!

Dev: ...

Manager: ...

Dev: fuck you

As of today I am no longer a Software Engineer. I am now a DevOps Engineer 🥳🥳🥳

And then one day you wake up and discover that your first boss,

the one who hired you when you had no experience

who believed in you when nobody else did

and also paid you a full decent payment when the rest of the world tried to pay you less than half the amount

who taught you a lot about the business and even when you disagreed, it was impossible to get angry because he was calm and gentle always

and treated you so many lunches and dinners

…was beaten and killed by a former colleague…

I have no words…

Sayonara 👋 boss
I will miss you so much on this Earth 😢

I had a boss I hated. Couldn’t stand him. Then I got a call saying my dad had collapsed and was at the hospital. I went into his office and told him I had to go because my dad was in the hospital.

“Why are you telling me?” he said. “Get the hell out of here.”

I looked at him quite differently after that.

Storytime!

Manager: Hey fullstackchris, the maps widget on our app stopped working recently...

Dev: (Skeptical, little did he know) Sigh... probably didn't raise quota or something stupid... Logs on to google cloud console to check it out...

Google Dashboard: Your bill.... $5,197 (!!!!!!) Payment method declined (you think?!)

Dev: 😱 WTF!?!?!! (Calls managers) Uh, we have HUGE problem, charges for $5000+ in our google account, did you guys remove the quota limits or not see any limit reached warnings!?

Managers: Uh, we didn't even know that an API could cost money, besides, we never check that email account!

Dev: 🤦‍♂️ yeah obviously you get charged, especially when there have literally been millions of requests. Anyway, the bigger question is where or how our key got leaked. Somewhat started hammering one of the google APIs with one of our keys (Proceeds to hunt for usages of said API key in the codebase)

Dev: (sweating 😰) did I expose an API key somewhere? Man, I hope it's not my fault...

Terminal: grep results in, CMS codebase!

Dev: ah, what do we have here, app.config, seems fine.... wait, why did they expose it to a PUBLIC endpoint?!

Long story short:

The previous consulting goons put our Angular CMS JSON config on a publicly accessible endpoint.

WITH A GOOGLE MAPS API KEY.

JUST CHILLING IN PLAINTEXT.

Though I'm relieved it wasn't my fault, my faith in humanity is still somewhat diminished. 🤷‍♂️

Oh, and it's only Monday. 😎

Cheers!

Management:

"We're gonna make our own builder that sets up pre configured files.

So we are gonna get rid again of GIT, because with our system you shouldnt be working over each others files if you keep out of other peoples files."

So they basically are saying, we are going back to no version control because you should all keep to the honor system because our system is better.

I'm fucking leaving...
And possibly leaving a poison pill to boot

I left a company once. Was there with one colleague and we had this kind of code review habit that we looked at each other changes befor merging them to the deploy branch. On my last day I made a dancing cat dance in front of our app as a tiny joke for him. He instead of reviewing just pulled this time and deployed the new version on the companies dev server without a look. So the fist time the cat showed up was appareantly in the first meeting after I left and everyone went completely crazy because they thought they got hacked.

I think they never found the hidden rock roll in the app.

Manager: You can’t define an async function without using await.

Dev: Yes you can.

Manager: Well you shouldn’t, there’s no point!

Dev: Yes there is. It can turn blocking synchronous logic into work performed concurrently. In this case the perform—

Manager: It’s called async *await*. Async *AWAIT*! Did you hear the two parts to that? You shouldn’t ever have one without the other. THEY GO TOGETHER. Worrying about concurrency is for people who use callbacks which just goes to show how out of date your skills are. I’m reading a book on javascript and there are so many advanced techniques out there that I haven’t even seen you use ONCE!

Dev: …

*I looked at the book he’s reading, it’s from the < ES6 era… no wonder he doesn’t see me using any of those archaic patterns/hacks/workarounds…*

Oh you're a frontend guy? Good, we need one of those.

Oh you're a backend guy too? Good, we need one of those.

Oh you're a security guy too? Good, we need one of those.

Oh you're a devops guy too? Good, we need one of those.

Oh you're a QA guy too? Good, we need one of those.

Oh you're an SEO guy too? Good, we need one of those.

"Well, sorry to say fullStackCraft, but we found your cloud architecture skills just a little too lacking for this position. We really need someone who can do frontend, backend, security audits, QA assessments, SEO, AND build scaling cloud architecture. Oh and while you're at it, can you turn fucking water into gold? We need that at our company too. You didn't get the position, but it'd be great if you could refer us to someone who is very advanced in fucking alchemy. Thanks!"

Absolutely toxic the way software people are treated I swear. The money may be the only good thing that is left.

Manager: Alright, we've decided we're gonna just going to accept PayPal and also credit card checkout through PayPal in the next two days!

Dev: ...

Manager: We can achieve this timeline, right?

Dev: ...

Manager: Alright, awesome to see your motivation! Let's do it!

Dev: YOU ANSWER PHONE CALLS, TALK TO PEOPLE AND 'STRATEGIZE' ALL DAY. YOU DON'T HAVE TO RELY ON THOUSANDS OF PEOPLE USING THE APP WITHOUT ERROR. THAT'S ON ME, NOT YOU, SO JUST SHUT THE FUCK UP!!!

Manager: ...

Dev: ...

Man do I love receiving bug reports and comments in Turkish, Russian, Portuguese or Iranian. I should really just start replying to those in Polish.

I added a humorous pinned post saying “By the way, I can only reply to you either in English, Polish or Dutch :)” to the program where I receive such reports.
I am aware it won’t do jackshit, because people can’t read.

Kurwa.

Ah yes. Fuck you

Manager: I’m so sick and tired of you devs whining about technical debt and how it’s slowing down our progress, so here’s the deal. You have until the end of this week to eliminate all technical debt in the codebase. After that I NEVER WANT TO HEAR YOU COMPLAIN ABOUT TECHNICAL DEBT EVER AGAIN!!!

Dev: …

Just learned that my employer withhold part of my salary every month the past 5 months! I did not notice it as it was overtime compensation.

I first thought maybe it was a mistake so I asked, the reply I got was: Oh you know that compensation we agreed upon? I wasn't having it anymore so I decided to half it and been since then editing the hours you billed every week to reflect that and accedently forget to tell you.

Accedently?! My ass! One week is believable but not 20 weeks. The only reason I found out is that they tried to lower the compensation even further which caused these hours to show up differently in the hour declaration software we use.

So currently on my way to return company's property and quit.

Manager: What’s taking so long on that PR?? It’s just some small styling adjustments

Dev: No it’s not you added an entire new calendar module that doesn’t work

Manager: Ok but besides that it’s just a small couple of css edits

Dev: You made styling changes in 50 files, half of which break our mobile responsiveness

Manager: Well then STOP talking to me and FIX IT if you’re so smart.

Dev: You also added a series of filters on a table in this same PR that cause th—

Manager: OK SO I GOT A BIT DISTRACTED THE FACT IS IT ALL NEEDS TO GET DONE SO IT DOESN’T MATTER IF IT’S ALL ON ONE PR SPLITTING THINGS UP INTO SMALL UPDATES IS JUST UNNECESSARY BUREAUCRACY AND IF YOU LIKE THAT THEN GO. WORK. FOR. THE GOVERNMENT!!!

Dev: …