Talks to Watch

The Worst Typo I Ever Made

6.4M views · Jun 1, 2020 · 11:25 · 2 HN recommenders · 4 mentions · discussed 2020–2026

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 Hacker News points people here: 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 comment, 2020

What Hacker News said 4

RecommendsrococosbasiliskAug 2020

“Tom Scott has a great video on his "Oh Shoot" moment”

Tom Scott recounts his worst code mistake.

Full comment

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

RecommendssneelaJul 2026

“Tom Scott, as usual, has a great video about the onosecond (sic)”

Tom Scott on the ohnosecond after a terrible mistake.

Full comment

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): this video

in “List of Humorous Units of Measurement” · view on HN
Cites itauroranilOct 2020

“Tom Scott made a mistake with a similar outcome as this article, but with an SQL query that is much more subtle than DROP.”

Tom Scott's subtle SQL mistake with destructive outcome.

Full comment

Tom Scott made a mistake with a similar outcome as this article, but with an SQL query that is much more subtle than DROP. this 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.

in “We deleted the production database by accident” · view on HN
Cites itSophiraOct 2021

“the worst typo he ever made in one of his prior jobs”

Tom Scott's worst typo from a prior job.

Full comment

Somebody just had their very own "onosecond". this 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.

in “Facebook-owned sites were down” · view on HN