Cognitive Engineering · Cognitive Engineering

Turning It On and Off Again

April 8, 2026·42 min·3 clips

Nick's router kept freezing, but turning it off and on again—a low-cost fix—made him wonder what really happens during a reboot.

1. Cognitive Engineering — hosted by Fraser McGruer with Nick Hare, Peter Coghill, and Chris Ragg of Aleph Insights — asks what actually happens when you turn something off and on again, and which systems could be rebooted. 2. Nick Hare prompted the episode when a stuttering video call was fixed by Peter telling him to power-cycle his router, leading Nick to wonder whether the logic generalises beyond computers. 3. The episode's core thesis is that 'rebootability' is a meaningful property of any complex system, definable by four criteria, and that applying these criteria reveals why some historical resets succeed and others fail. 4. Peter explains that routers crash because software is imperfect: memory leaks, zombie processes, corrupted network address tables, and even cosmic rays flipping bits can push the machine into a bad state that turning off and on resolves by returning it to a known good state. 5. Peter defines 'state' formally: if you need to know something about a system to predict how it will respond to an input, that system has a state — illustrated with an oven's plus-button behaving differently depending on whether it starts on five or eight. 6. Peter's first criterion for rebootability is whether the good state is stored externally: a router's firmware lives on read-only memory separate from working memory, so the working state can be cleared and the instructions re-read; the climate has no backup of glacier.exe. 7. The panel draws the analogy that the US Constitution functions as the ROM for America — a written external document that defines how to be America at a minimal level — and that 1776 would be the restore point if the entire legal system were wiped. 8. Nick raises the German Weimar hyperinflation as a successful monetary reboot: the Reichsmark was abandoned and the Deutsche Mark introduced on a single Sunday, with everyone receiving an initial allocation and agreeing to the new shared myth that money has value. 9. Peter's third criterion is consensus: monetary systems, like operating systems, only work if everyone agrees to run the same version, which is why the French Revolutionary 10-day calendar week failed — a software update nobody downloaded. 10. Chris introduces fundamentalism as the extreme conservative case: not only should you revert to the original state, you should never have deviated from it — a position that, historically, prevents evolution and innovation. 11. Chris raises Noah's Ark as a flood-myth reboot: God deletes a corrupt world and seeds it from a tiny backup, but the underlying question is whether humanity is 'save-locked' — doomed to return to the same error state regardless of how many times the system is reset. 12. Peter's fourth criterion is path dependency or hysteresis: some systems reach a point from which there is no direct path back to the good state, requiring transit through intermediate states or remaining permanently in the error state — illustrated by rainforest collapse leaving degraded soil that cannot support tree regrowth. 13. The group links path dependency to political systems: a dictatorship that abolishes elections eliminates its own restore point, and the 'last few commits have been terrible, rewind to there' impulse of conservatism is critiqued as a misreading of which variables actually made the good state good. 14. Peter introduces the bootstrap problem as the second criterion: a system can only be rebooted by something outside itself — a Windows CD-ROM, a car's starter motor — and the national grid 'black start' scenario illustrates the danger: if all substations fail simultaneously, power stations cannot restart because they need electricity to generate electricity. 15. Post-war Germany and Japan are treated as successful reboots: Allied external bootstrapping, combined with genuine consensus on a new state, produced pacifist democracies within 20 years despite deep prior ideological entrenchment. 16. Iraq and Afghanistan are treated as failed reboots — Chris frames the failure as imposing an operating system from System A onto System B and assuming compatibility, when the underlying system architecture is incompatible. 17. The episode's tone is collegial and exploratory, with four analysts building on each other's frameworks in real time, occasional self-deprecating humour ('not very interesting because I just didn't understand what Peter was talking about'), and no firm conclusions. 18. The closing segment invites personal favourite resets: Nick cites the COVID lockdowns as a partial societal reboot; Peter describes fainting at 14 as a brain reboot ('literally like a rebirth'); Chris cites quitting his analyst job to go to Honduras and become a dive master, which set him on a path to documentary photography. 19. Listeners interested in systems thinking, political philosophy, or the analytical framing of everyday observations will find substantial material here. 20. Listeners wanting applied advice, empirical evidence, or resolved conclusions rather than exploratory framework-building will find the open-ended format unsatisfying.

As heard by us

A reset is never just a reset.

The episode opens with a router anecdote, then widens into a plain but sturdy argument about what rebooting can mean for people, systems, and societies.

Read the full review in PlayNext →

Why you'd press play

When you need a smarter answer than "just turn it off and on again."

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Cognitive Engineering