error handling

3Blue1Brown's discovery-oriented introduction to error correction codes, building up Hamming codes from the puzzle of locating a flipped bit. It explains the parity-check idea and why it is so efficient.

Veritasium explains how cosmic rays and other particles flip bits in computer memory, with examples including a Belgian election count error, plane incidents and game glitches. It is inspired by a RadioLab episode on bit flips.

NASA's animated explanation of the Curiosity rover's Mars landing, which relied on a complex automated sequence taking about seven minutes. It features NASA engineers discussing the risks before the 2012 landing.

Veritasium builds a QR code by hand to explain how it works. It covers the history of Morse code and barcodes, how QR codes encode data, why damaged codes still scan, and how safe they are.

Tom Scott explains for Computerphile why handling time and timezones in code is so hard, walking through a simple web app that computes how long ago something happened. It covers the quirks of timezones and calendars and ends in an exasperated rant.

3Blue1Brown visualizes the Riemann zeta function and the analytic continuation that extends it beyond where its series converges, building toward the Riemann hypothesis.

MinutePhysics explains that computers store brightness nonlinearly, so blurring and blending colors in raw RGB gives wrong, dark results. It shows why mixed colors, such as in gradients, look off.

3Blue1Brown's second neural network chapter explains cost functions and gradient descent, showing how a network learns by minimizing error during training.

Verge Science's pilot of its Trial & Error series follows amateur scientist Jon Larsen on a hunt for micrometeorites. It shows how tiny space rocks can be found on rooftops and confirmed under a microscope.

An MTA video on communications-based train control, the system meant to replace the New York City subway's century-old signaling. It also shows the mechanical interlocks and signals in use today.

Technology Connections explains the difference between power (watts) and energy (watt-hours) and why confusing them leads to errors. It runs about 52 minutes and uses everyday examples.

Tom Scott explains for Computerphile how floating point numbers work, why moving the binary point is fast, and why it handles money badly.

A short Coding Secrets episode explaining why hitting a Sonic 3D cartridge triggers a hidden level select. The cause was a custom crash handler that redirected CPU error interrupts to the level select screen.

Matt Parker of Stand-up Maths explains why people keep making the same mistake with millions and billions, using a Bloomberg cash calculator example. He looks at the unit slip behind the repeated arithmetic error.

Tom 7 (suckerpinch) delivers a long, comedic digression on gradient descent and floating-point imprecision. He shows how rounding behavior can supply the nonlinearity needed to build a neural network.