The Worst Typo I Ever Made

Tom Scott has a great video on his "Oh Shoot" moment ( [VIDEO] ). Thinking back on the times I've had code exist nowhere else but the clipboard...

Tom Scott made a mistake with a similar outcome as this article, but with an SQL query that is much more subtle than DROP. [VIDEO] By all means, find ways to fool-proof the architecture. But be prepared for scenarios where some destructive action happens to a production database.

Somebody just had their very own "onosecond". [VIDEO] The video is one that Tom Scott published in June 2020 about the worst typo he ever made in one of his prior jobs, and while the Facebook mistake is almost certainly not going to be anything irrecoverable like this one, you can bet that Facebook pride themselves on being available all the time.

The good ol' Ohnosecond: > An "ohnosecond" is the second after one makes a terrible mistake, such as deleting the wrong file or sending a text message to the wrong person, where the person in question can do nothing but say "oh no". The term is believed to originate from Elizabeth Powell Crowe's 1993 novel, The Electronic Traveler. Reminds me (and probably a lot of devs) of a time when I deployed something breaking to production many years ago :), of course I didn't know it would break production beforehand. Recently, I accidentally deleted my entire shell history which caused me quite a bit of slowdown for some time. I'm quite used to modifying complicated commands with Ctrl+R and fzf; the deletion of my shell was truly horrifying. Tom Scott, as usual, has a great video about the onosecond (sic): [VIDEO]