The Worst Typo I Ever Made

Channel:Tom Scott · Length:11:24 · Published:2020-06-01 · Views:6413623

Watch on YouTube

Summary

Tom Scott recounts the worst typo he ever made, a subtle mistake in code with destructive consequences at a previous job. It is a cautionary tale about irreversible operations.

Why HN recommends it

Shared in outage and accidental-deletion threads as a relatable, well-told horror story.

Tom Scott has a great video on his "Oh Shoot" moment — HN, 2020

Testing, debugging & developer tools · Software practice, open source & careers · Databases & storage

Subtitles (excerpt)

The “onosecond” is the second after you make a terrible mistake. The second when you realise what you just did and that there’s nothing you can do about it, the second when all the now-inevitable consequences flash through your mind. It is the second after you send a text message to the wrong person, after you delete the wrong file, after you spill the secret that you thought they already knew. The “onosecond” is that stomach-dropping, breath-stopping moment when all you can do is say “oh, no”. This is the story of the worst typo I ever made. I was maybe 18 or 19, in charge of converting an old web site to a new and faster platform. A half-dozen volunteers had spent days transferring all the articles over, copying them from the old site, updating them, and then saving them in their new place. It had been a lot of effort, but everything was pretty much sorted now. There was one thing I needed to do: a search-and-replace across all those pages of content. And I was wise to the mistake that people usually make there: it’s called the clbuttic mistake, where someone wants to censor the word “ass” and the search-and-replace gets a little bit more enthusiastic than they thought it would. This problem: much simpler.

On Hacker News

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… — sneela, 2026-07
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... — rococosbasilisk, 2020-08
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. — Sophira, 2021-10
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. — auroranil, 2020-10

Related videos