The Worst Typo I Ever Made
Tom Scott2 HN recommenders · recommended in 2 months, 2020-2026
6.4M views · 6 years ago · commentary · evergreen
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.
Shared in outage and accidental-deletion threads as a relatable, well-told horror story.
1:06:44Programming is terrible—Lessons learned from a life wasted. EMF2012
tef ebooks
1.7M views • 13 years ago
4:31why typing like this is sometimes okay.
Tom Scott
5.4M views • 7 years ago
30:58Emojli: Behind the Scenes and Why You Should Never Build An App
Tom Scott
1M views • 12 years ago
45:50"The Mess We're In" by Joe Armstrong
Strange Loop Conference
398K views • 12 years ago
22:15Badness 0 (Apostrophe‛s version)
suckerpinch
258K views • 2 years ago
36:31Hey Underscore, You're Doing It Wrong!
InfoQ
141K views • 13 years ago
29:25Rust NYC: Jon Gjengset - Demystifying unsafe code
Rust Programming Language
27K views • 6 years ago
7:53How the US Postal Service reads terrible handwriting
Tom Scott
7M views • 4 years ago
1:01:59Null References: The Billion Dollar Mistake - Tony Hoare
JoseCan
66K views • 7 years ago
44:35Object-Oriented Programming is Bad
Brian Will
2.6M views • 10 years ago
26:4210 Things I Regret About Node.js - Ryan Dahl - JSConf EU
JSConf
662K views • 8 years ago
10:13The Problem with Time & Timezones - Computerphile
Computerphile
4.4M views • 12 years ago
25:41Compiling C to printable x86, to make an executable research paper
suckerpinch
479K views • 9 years ago
22:41"Clean" Code, Horrible Performance
Molly Rocket
1.2M views • 3 years ago
56:13I don't like notebooks.- Joel Grus (Allen Institute for Artificial Intelligence)
O'Reilly
120K views • 8 years ago
6:44I was wrong (and so was everyone)
Tom Scott
5M views • 3 years ago
44:29Breaking the x86 Instruction Set
Black Hat
381K views • 9 years ago
54:53Miguel de Icaza: Swift Godot: Fixing the Multi-million dollar mistake #GodotCon2023
Godot Engine
27K views • 3 years ago
12:31OSCON 2010: Rob Pike, "Public Static Void"
O'Reilly
119K views • 16 years ago
1:29:27The Forgotten Art of Structured Programming - Kevlin Henney [C++ on Sea 2019]
cpponsea
245K views • 7 years ago
4 comments from 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 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
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.
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.
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...