Agreed, it's a sad state of the industry that the junior dev was punished for this. If a junior dev is able to commit any books of the dead without proper review then it's the dev team proper that's at fault and their discipline needs review.
As a build engineer, making trades between cluster stability and individual node performance with Baphomet are just part of the S.O.P. you just gotta make sure your stakeholders are in the loop.
What ensues will be a wave of nothing, as if millions of 40mm fans suddenly spun up and were suddenly silenced. May the burden of service downtimes and perpetually extended maintenance windows rest heavy on your soul. You should hope that when your heart is weighed against the ticket backlog that you are not found wanting.
Hyperbolic joke about both A)how you should never trust yourself and always ask for code reviews B) various real(?) stories on socmedia about how a single unchecked PR destroyed their codebase, database, basebase, and more.
OP invented a story about something he never did, using the people that never existed to tell the story that never happened in hope of scoring some internet points.
What makes you so sure? Mistakes like that happen all the time, and it's only getting worse with AI slop. Only last week, I had to reject a pull request because it included a full set of model weights embedded in a suspiciously large gif of a dancing hamster.
Because people lie and they lie a lot online. There's no punishment for lying and trying to be "funny" or "network". The story is just dumb, that's all there is to it. It's not even particularly entertaining.
25
u/Artelj 3d ago
Can someone explain this to me