Men only want one thing, and it's fucking disgusting

From now on -and until further notice- I'll commit heinous crimes against each and any developer blaming GPT when their code is BAD.

YOU are in the workforce. Not GPT. YOU are responsible for the shit you write.
There is a reason GPT costs 200 bucks per month and you cost at least ten times as much. Own your mistakes, learn to code while you still have time, before the chatbot actually catches up and makes you obsolete.

Sincerely signed: the guy who straight up refuses to install copilot. I'm perfectly capable of introducing my own fair share of bugs, without relying on some autocomplete plugin.

Team Leader, once again, wagered I was wrong on a technical thing
I, once again, accepted his wager

Team Leader, once again, lost the bet.

That's 3-0 now.

- A colleague introduced a regression through an error nobody would ever think of (as in: the code broke in a way no sane person would ever guess)
- I noticed the regression in develop, tried to pull a sneaky fix to avoid causing troubles
- Permissions got switched up in the past 2 days or something, I'm not listed as a releaser anymore
- Talked to my TL, he accepted my PR but said "I can't give you the releaser role anymore"

So, I tried at the same time helping out a colleague without causing a fuss and improving the product, and lost a role in the process. Love to see it.

ooooh, this gon be god

I will never understand how some retarded angular dev will overengineer a trivial HTTP request, make it an observable and feel like they're the most clever guy on earth

WHAT GOES AROUND COMES BACK AROUND

Overflooded with tickets about regressions, management finally gave in and instructed us to use integration tests again.

Who would have seen that one coming.

(at least half of these "regression tickets" were not regressions at all, but I'm not going to be the one spoiling the first time management actually makes the right call)

The full switch statement is actually twice as long as this thing here

Currently working on a new feature on some old undocumented part of the code born out of the bastard fork of draw.io -back when it was opensource- and without a doubt the hardest part of it all is using GIMP TO DRAW A FUCKING ICON WHICH IS THE SAME AS AN OLD ICON WITH ONE MORE LETTER ON TOP I WANT TO DISEMBOWEL WHOEVER DESIGNED THIS PIECE OF SOFTWARE

You heard it first, if the next project isn't assigned to me I hand my 2 weeks notice and push farts to master.

Enough.
Is.
Enough.

> People: Mister IHateForALiving, the external consultant who took care of the new client is about to leave :) his leader is searching for someone to help him and build the new features :) we think you should be doing it, you're very good with the frontend

I WILL NOT FIX
YOUR FUCKING
TECHNICAL DEBT

You fucking moron of a "tech lead", working like a human was free; you chose to work like a dog and encouraged the external consultant to work like a dog as well. From now until you resign, this mess is yours to clean.

What's that? The coolest mug ever? I would never.

We were delaying a feature from the roadmap because implementing it in the new client was taking it days we didn't have.
One of our devs backported everything in the old client, some undocumented clusterfuck of crusty code from 12 years ago running in AngularJS.

Oh my, if it isn't the same fucking thing I've been calling for THE ENTIRE PAST YEAR

> CTO: I developed this product, I know it to the core! It's been stable for years, safe and rich in features, how is it even possible that things got so complicated?

The product he developed:

Oooh you're such a nasty rebellious little punk, a threat to society indeed.
Get fucked.

Yes, of course I work with DDD

Desperation Driven Design

The worst part is: this commit message would cost me my job, but whoever created this retarded mess of multiple responses is untouchable.

My old comments are a mood

Love working alongside Angular devs, I wanted to add a page with a table and a modal, ended up creating something like 15 files and I'm not even halfway through, must be nice living with a brain the size of a pea.

THE CURSED SPAWN FROM 20 GENERATIONS OF INBREEDING ALL ENDED UP IN MY FUCKING COMPANY

Someone at this point MUST have realized this was excessive, and this someone kept going nonetheless

Coding lessons 101, it shouldn't be that fucking hard to understand what a pointer is but that's where we currently stand

I want to know the name of the evil mastermind who once conceived the "literal" function in Sequelize.

- You design a method to insert pieces of raw SQL exactly the way they are written, no further processing
- You release this method, you call it LITERAL to make sure people know its intended purpose: it is used to insert LITERALLY everything you write, nothing more and nothing less
- Then make sure this "literal" method changes the fucking case of column names. Because that's what "literal" means in the head of this rabid animal: you arbitrarily change the code written by the developer

WHY
WHY ARE ALL AR ORM DESIGNED BY FUCKING ANIMALS
ELOQUENT IS TRASH, SEQUELIZE IS TRASH, TENS OF DEVELOPERS AT WORK TO ALCHEMICALLY CREATE THE MOST ROTTEN CODE THEY POSSIBLY CAN, BECAUSE YOU MUST NOT BE ALLOWED TO WRITE ANY QUERY MORE ADVANCED THAN "SELECT * FROM users WHERE id =1", NOT A FUCKING SHRED OF DOCUMENTATION AND 16 MILLION LAYERS OF ABSTRACTION TO MAKE SURE EVERY BUG FUCKING STAYS THERE, DON'T YOU DARE TO USE A JOIN, DON'T YOU DARE TO TREAT A DMBS LIKE AN ACTUAL FUCKING DBMS INSTEAD OF A HOT STEAMING PILE OF METHODS IMPLEMENTED BY MONKEYS.

+++ THEY ARE WRITING TYPE DEFINITIONS +++

THEY ARE UNDOGGING THEMSELVES. THIS IS NOT A DRILL: THEY ARE LEARNING SOME GOOD FUCKING PRACTICES

Voice call with the whole dev team

Former team leader: Yeah, basically we stopped using RxJS because it ended up being too complicated, every minor problem required so much code to solve :(
IHateForALiving, extremely loudly: WELL WELL WELL, GOOD FUCKING MORNING, SUNSHINE

MICROSERVICES ARE NOT A SUBSTITUTION FOR GOOD DEV PRACTICES, IF YOU WERE A WERECODER BEFORE MICROSERVICES, A MIGRATION WILL NOT TEACH YOU/YOUR TEAM HOW TO CODE.

> barges in
> slams massive unintelligible PR on the table
> fixes a bunch of tickets all at once
> won't explain how tf it works, it just does
> refuses to elaborate further
> leaves

- TeamLeader1: Noooo, classes in JS are fake because here and there, in NodeJS they work differently from the browser because here and there, I know it
- IHateForALiving: I'm betting 50 cents against 50 bucks that you're wrong. You in?
- TeamLeader1: Uhm... no, I don't feel like betting against you about technical issues :(

It's been a months long journey, but it finally looks like we're getting somewhere.

THE TALE OF THE CRAZED VISIONNAIRE

Once upon a time some masochist woke up and snorted a gallon of glue. "I NEED PAIN", he shouted, and then proceeded to hammer down his own cock over an iron anvil, in an effort to uncover the most intense pain a human could experience. And yet even such a punishment was not enough, for our pain-starved hero thirsted for even higher heights. "This hammering can't satisfy my spirit", he proclaimed; "I shall find ever greater pain than what little solace these tools can provide, but it's much too hard a task for a single mortal to complete in one lifetime. And lo, I will gather around me the bravest and uncover the intense sorrow no human has ever experienced before!". And for his journey he found himself a loyal fellowship, all striving to find the ultimate pain a mortal can experience.

"But who could be crazy enough to follow a glue-fueled schizo who hammers their own genitals?", you might stupidly ask. But why, the JS community of course.

> TeamLeader1: I just discovered SQL is actually super fast! The low responsiveness I've experienced comes from our ORM!
> IHateForALiving: well of course SQL is blazingly fast. SQL has been refined by the best engineers in the world for the past 50 years, its performances are unparalleled for everything you could possibly need, unless you want to scale REALLY big. Sequelize, instead, is an Active Record ORM, so it's bound to struggle with huge amount of data, because every single row will get attached a significant amount of black magic to make sure everything syncs correctly. Why is that?
> TeamLeader1: I have a problem with this frontend component, it doesn't allow pagination. I tried downloading the whole DB to bypass that, but the ORM is slow... so I will bypass the ORM and download the whole table with a raw query. Look at that! It works like a charm, it's super duper fast!'

This mf is downloading some 35 thousand rows every time some user loads a page because he doesn't know how to paginate the fucking table with Angular, there's no way these people are real.