WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

1.0K

Creating an unintended catastrophe is a right of passage. Mine was on a HP-UX system in the late 90s.

Creating an unintended catastrophe is a right of passage. Mine was on a HP-UX system in the late 90s.

(post is archived)

[–] 4 pts

Yet another success-story!

[–] 2 pts

Good one. Actually a funny story not involving pajeets or DEI.

[–] 1 pt

A friend of mine, former coworker, he installed a cron job with a custom python script on our prod ETL servers one time that took the entire app down. He misused the fileinput module in one line of code and essentially fork bombed the server. I forget the details, but if I remember correctly it overwrote a bunch of files with itself like a virus, and it would just continue executing itself until the box seized up. This cron job was supposed to run like every five minutes, so we had only that much time to troubleshoot wtf was happening after a reboot before the box dropped off again. Good times. He doesn't use fileinput anymore.

[–] 0 pt (edited )

I have rebooted a prod server unintentionally during peak hours. Shit happens.

If you don't learn from it, that shit is on you.

Also, no, it was not near that scale but it was noticed.

[–] 1 pt

Got a few guys here who got burned doing something without a ticket. One of them is anal to the max now post getting written up for it. Kinda a stupid reason, too. Now it's no ticky, no worky.

[–] 0 pt

You remind me of the old HP3000 I used to work on. All my changes went straight to production because that didn't have the concept of dev/stage/prod. Good times!

[–] 1 pt

I had the same issue. I at least made changes either very early or late in the evenings. Never on a weekend. I hate that bitch I worked for.