That feeling in the pit of your stomach when your DELETE SQL statement that should have completed in a split second still hasn't completed.
(Thankfully not me this time, just cringing in sympathy after I heard someone else's tale)
That feeling in the pit of your stomach when your DELETE SQL statement that should have completed in a split second still hasn't completed.
(Thankfully not me this time, just cringing in sympathy after I heard someone else's tale)
One of the times - oh yeah, somehow there was a transaction lock on the database from something else happening. So it wasn't anything I did.
The other time ... Well, let's just say the DBAs got a plate of cookies from me the next day.
@hal_pomeranz But just this ONE time? I mean it's such a quick little change. Surely nothing could go wrong just this once...
@JessTheUnstill Always SELECT before DELETE, like you “ls” before you “rm”. Let’s be careful out there!
Also, I'm pretty sure I've said this before, but I'll say it again:
Part of your job as a senior is to tell your juniors about your fuckups. The embarrassing cringe reckless and lazy bullshit that you did when you were new, and the various times you brought down Prod. We ALL did it sometime. And then tell them: the moment you realized you fucked up, I know, the impulse is to try and cover it up, but don't do it. Come to the seniors you trust, and they'll help you unfuck it, and fight management tooth and claw like mamma and pappa bears to defend you from any shitheads in management. Because that's what our seniors did to us.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.