Locknote: Programming’s Greatest Mistakes - Mark Rendle - NDC Oslo 2022

Most of the time when we make mistakes in our code, a message gets displayed wrong or an invoice doesn’t get sent. But sometimes when people make mistakes in code, things literally explode, or bankrupt companies, or make web development a living hell for millions of programmers for years to come.
Join Mark on a tour through some of the worst mistakes in the history of programming. Learn what went wrong, why it went wrong, how much it cost, and how things are really funny when they’re not happening to you.
Check out more of our featured speakers and talks at
ndcconferences.com/
ndcoslo.com/

[@buddy2762]

I'm never going to give up on scanning QR codes, they never let me down. They don't run around and desert you.

[@Hans-gb4mv]

Hey, you should have added a spoiler alert...

[@anon-fz2bo]

lmao knowing mark i knew it would be something stupid 🤣

[@miv6770]

Mr. Stanislav is a hero - we should wish more people would be like him, actual brilliant engineers with the ethical values to do the right thing. This however needs a certain culture, upbringing, responsibility, values, ethics, which are in short supply lately especially in the salaries-driven fake-it-till-you-make-it "tech" world.

[@dynfoxx]

Good talk. Quick note Rust optionals of pointers are the same size as normal printers. If you were going to check your pointer for null there is no size or performance overhead of Rust optional.

[@Andrew-jh2bn]

I believe this optimization also applies to any data type that has an invalid binary representation. I.e. if your data type can never be represented by all zeros ( like pointers, strings, vec, references and more) the none variant is represented by all zeros with no overhead. This can work even for enums you declare yourself.

[@JohnDlugosz]

17:00 My first thought was that it's the illustration of the Krebs Cycle in biology, used as a parody. Of course, now that I thought of that...

[@tomekpisula6626]

Always a good watch

[@edgeeffect]

"I'm basically going to talk bollocks, but I might accidentally teach you something".... Hmmmmm.... sounds interesting. I think I've watched the version with all the mistakes in before... this one is much better.... I like the swearing too! Ariane 5... not only did they copy and paste... they also copy and pasted some of the most awful code you will ever see in your entire life.

[@PaulSebastianM]

41:30, well, on the other hand, you do drive on the "wrong" side of the road...

[@fenrirwulf9266]

This is a reupload. What happened to the original?

[@deus_ex_machina_]

Nothing happened. It's still up here: kzbin.infoYfKzJuXmZX8 And the Copenhagen version of the talk from August '22 mentioned at 4:20: kzbin.info/www/bejne/p3TCmqKAhtWpaqc

[@WorstDeveloper]

Video starts at 2:40

[@pkoch]

Real MVP ❤

[@Rx7man]

This really reminded me of Tom Scott's worst typo ever kzbin.info/www/bejne/jmexe56Nl7Jkrs0

[@GeorgeTsiros]

44:00 no, not ariane 4 (four). Ariane 5 (five).

[@brynyard]

It's not that Lockheed Martin will _stop_ making bombs, it's much more worrying when they _start_ making bombs "for" you :P

[@JohnDlugosz]

26:34 er... wasn't ALGOL W created by Nicolas Wirth? Checking Wikipedia... OK, it seems C.A.R. Hoare was also involved, though that's not so well known. Looks like it wasn't _called_ ALGOL W until later, when Wirth continued working on it after it was turned down by the ALGOL language committee.

[@kahnfatman]

SAF3 as f**k