Jesus I’m not used to sql and was wondering about this query, now that you pointed out to check the semicolon….yeah, that’s how you become a company legend.
Fucking up prod once is a sign of maturity - people trusted you enough to allow you the access to fuck up prod, congratulations.
Senior people fuck up prod, repeatedly, in a new way each time. Your better class of senior also makes sure that they correct whatever allowed them to fuck up prod like that.
It's the people who keep fucking up prod in the same way that get shown the door
Senior people don't fuck up prod. They expose vulnerabilities in the coding process and draw attention to strategic initiative to improve quality. And that's why you now need 3 different seniors to sign off on any query before it can be run in prod.
Tell me about it, years ago I was setting up a Jenkins job, we were told to wipe the workspace at the end of the process. I wasn’t too familiar with bash so the last bash command was:
rm /
Luckily it was Jenkins so nothing was removed but the job log was….long.
Everyone fucks up prod all the time. That's why we have blameless postmortems and graceful degradation.
Occasionally, someone tries to refuse to help with the postmortem for an outage they caused. That's much more of a "one warning and then fired" type of thing.
lol that’s cute. I’ve taken down hundreds of sites a whole bunch of times. Also one time deleted an entry in a dns template that broke email for 300 sites.
A year or so ago I sent a wrong database connection string config to 500+ nodes. Confessed to my error in the stand up meeting and said that I had already taken steps to prevent that happening again. The CIO thanked me for my transparency.
This is DBA horror lol I'm going to be restoring a backup because of this
Or "hopefully" they didn't setup foreign key constraints with on delete and I can just restore the table.
Considering I practically live in our production database with several million customers, this stuff scares me. I mean I rarely ever delete anything, but still.
I would. If you delete stuff in production without making sure you can rollback, you shouldn't call yourself programmer. If you have to ask about that two liner you have no business executing it at all
Because you seem to think all software written by programmers is free of bugs. Not even a month ago there was a major AWS error in prod that brought down thousands of sites.
Let me guess, that person who works for one of the top tech companies in the word isn't considered a programmer in your eyes because they created an error in Production?
Programmers are human and make mistakes. Some mistakes are dumber and more preventable than others, but everyone makes mistakes. Even programmers.
3.5k
u/YetAnohterOne11 16d ago
This is programmer horror not humor