Gary, Year 3

The reason the gyroscope story got demoted is a lovely experiment. A group built a bike with a second wheel spinning backwards to cancel the angular momentum, and arranged the geometry so trail was not doing the usual job either, and it still self stabilised when rolled. So neither gyroscopic effect nor trail is strictly necessary, which killed the idea that either one is the answer on its own.

What is left is: self stability comes from the whole system, and any design that steers the wheel into a lean fast enough will do it.

The physical part in one line: fog appears when the glass is below the dew point of the cabin air. Two ways to prevent it, lower the moisture in the air or raise the temperature of the glass. Heating the glass is what your demister does and it is slow. Removing the moisture is what the air conditioning does and it is the one people leave switched off in winter because it feels wrong.

Practical constraint that helped me: give yourself a page budget. One page, one screen of copy, one screenshot, one button. No framework, plain HTML if you like. If a change does not fit in that budget it does not happen. Constraints remove the decisions that the perfectionist part of you uses to keep the loop going.

That overstates it. There is no single agreed dominant mechanism, but there are several well understood contributing ones, and most of the argument is about experimental conditions rather than a gap in thermodynamics.

The endpoint point is what changed my mind. I ran this in a lab freezer for a teaching demo and got the surprising result three times out of five with a surface crust and zero times with a centre probe.

This also protects you from building the wrong automation. I automated a workflow before I had done it manually and got it structurally wrong, which cost more to unpick than doing it by hand for two months would have.

Lead with Newton, because it is the version that stays true when she pushes on it.

A wing pushes air downward and the air pushes the wing upward. That is the whole thing. You can point at a helicopter, a propeller, and a hand out of a car window and all three are the same sentence. It also handles the things the pressure story confuses beginners about, like why a plane can fly upside down and why angle of attack matters so much.

The pressure description is not wrong, it is the same physics viewed at the wing surface rather than in the air being moved. The version that is genuinely wrong is the one usually taught, which claims air splitting at the front must meet up again at the back. It does not, and the air over the top actually arrives sooner.

Demo: flat hand out of a moving car window, palm level, then tilt the front edge up a few degrees. Her arm gets shoved upward and she can feel the air being pushed down. Ten seconds, no equipment, and it is the real mechanism.

The wall is real and it is not about you. Hypothesis testing is where most books switch from explaining ideas to teaching a procedure, and the procedure is genuinely unintuitive when it arrives without motivation.

What got me through was reading two kinds of book at the same time. One narrative book about how statistics goes wrong in the world, which gives you the reason to care, and one working book where you do things with actual data. How to Lie with Statistics is very short, decades old, and still the best cheap introduction to why any of this matters. The Signal and the Noise is the longer modern version of the same instinct.

Then for the doing part: pick a dataset you personally care about, something like your own running times or your electricity use, and answer one question with it. The formulas stop being formulas about nothing and start being answers to a question you actually asked.

It is exposure, not resolution. The moon is a sunlit rock. It is being lit by exactly the same sunlight that lights your street at noon, so the correct exposure for it is roughly the daylight rule, something like f/11 at 1/125 second at ISO 100.

Your phone sees a frame that is 99 percent black sky, decides the scene is very dark, and opens up by six or eight stops. The moon is then massively overexposed and clips to pure white. Your eyes do the equivalent of local metering, which is why you see detail and the phone does not.

The fix on any modern phone: tap on the moon to focus, then drag the little exposure slider down, usually a long way down, until the disc stops glowing and you start seeing grey patches. On most phones that is between two and four stops of negative compensation. If you have a pro or manual mode, set ISO 100 and shutter around 1/125 and you will get craters immediately.

Use the optical telephoto lens if the phone has one, and stop before digital zoom takes over, because past that point you are just enlarging pixels.

One risk of automating first that people underrate: once the machine is producing it, you stop reading it closely, quality drifts, and you do not notice until someone unsubscribes. The manual version keeps you honest for as long as you can stand it.

Humidity, or more precisely how close the outside air already is to saturation.

Your breath leaves at roughly 35C and essentially 100 percent relative humidity every single time. What happens next depends entirely on the air it mixes into. The saturation curve is strongly nonlinear, so when a warm wet parcel mixes with a cold one, the mixture can briefly hold more water than it can carry at its new temperature, and the excess condenses into the fog you see.

If Thursday's air was dry, the mixture stayed under saturation the whole way and there was nothing to see. Damp mornings after rain fog beautifully at temperatures where a dry cold snap gives you nothing.

For the science part, tell them big crystals need slow growth and few starting points, and fuzzy crystals mean too many starting points at once. The same rule shows up in fudge, in honey going grainy, and in metals cooling. It is one of the more transferable kitchen lessons going.