You must log in or register to comment.
“good morning, I’m about to destroy the backend” is exactly the energy I’d welcome from a colleague frankly.
I think the outage that followed as we fumbled to replace it would probably be cheaper than the ongoing maintenance after a few months
I’ve seen plenty of back ends that needed to be destroyed.
Are we still talking about code?
Wait, you guys were talking about code?
What is this magical job where two typos land you a day off, no questions asked?
A typo in software development or other shell based work could completely ass womp a system in ways that could lose a company lots of money.
Oopsies on prod systems, even with an outage window, can really fuck shit up. Seemingly small mistakes can quickly snowball into systemwide outages.
It’s wild to me how some places I’ve worked are like locked down, all the infrastructure is in terraform or whatever and can be deployed immediately… and other places are like “ssh into prod with the credentials from confluence, edit the config in vim, and paste the new code into a new file”
Tech CEO
In my last job we called that “optimizing”, after a colleague (who usually only did frontent work) used the opportunity when everyone else was on vacation to implement a few show-stopping bugs in the backend and put “optimized backend code” in the commit message. He did the same thing a few months later during the next vacation period, which really solidified the joke.
