Cognitive Engineering

Episode summaryIn this episode, the team explores what prizes are actually for. Starting with a discussion of FIFA’s much-mocked “Peace Prize” and the longer pedigree of the Nobel Peace Prize, they examine how prizes gain prestige, whether they genuinely incentivise good behaviour and how they can shape status, motivation and public recognition.The conversation moves from global peace prizes to personal experiences of winning school and university awards, before turning to the deeper question: what makes a prize valuable? Is it age, scarcity, continuity, the calibre of previous winners or the significance of what it rewards?The episode ends with the proposal of a new award: the Aleph Peace Prize, aimed not at symbolic virtue but at people or institutions that have plausibly reduced the risk of actual conflict.In this episodeWhy FIFA’s “Peace Prize” is seen as absurd and performativeWhat the Nobel Peace Prize was originally meant to rewardControversial Nobel winners, including Henry Kissinger and Barack ObamaHow Nobel Peace Prize winners tend to fall into categories such as:peace process participantshuman rights advocatesinstitution buildershumanitarian organisationsWhether prizes are mainly about:incentivesrecognitioncredentialisationrewardWhy prestige depends on factors like age, continuity, scarcity and past winnersThe idea that too many prizes can dilute the value of all prizesPersonal reflections on school and university prizes, and how recognition can affect confidence and effortA proposed alternative peace prize focused on real-world conflict reduction

In this episode, Fraser McGruer, Nick Hare, Chris Wragg and Peter Coghill explore one of modern life’s most persistent irritations: being asked to create yet another username and password.The conversation starts with a familiar frustration—setting up endless accounts for everyday tasks, from charging an electric car to buying a coffee—and quickly broadens into a deeper discussion about identity, convenience, data and the trade-offs built into digital life.Why do so many companies want us to log in all the time? Is it really about making life easier, or is it about harvesting data? The team examines the competing incentives at work: users want speed and low friction, while businesses want persistent identity, customer lock-in and as much information as possible.Along the way, they distinguish between situations where accounts are genuinely useful and those where they feel completely unnecessary. They also explore how the digital world has transformed ordinary interactions that once depended on human recognition and informal trust into bureaucratic login rituals.Nick introduces a “new account nuisance matrix” to sort the helpful from the pointless, while Peter outlines the technical case for more robust digital identity systems—without handing all power to Google, Apple or the state. The discussion ends with a look at possible solutions, including the idea of self-sovereign identity, where users retain control over their own credentials and data.In this episode:Why account creation feels so relentless nowThe trade-off between convenience and data harvestingWhy companies want persistent digital identityThe technical reasons accounts can be usefulWhy some logins feel justified and others feel absurdThe differences between digital and analogue identityThe nuisance of fragmented sign-ins and password fatigueWhy centralised digital identity systems may be riskyThe case for self-sovereign identityKey ideas and concepts:Greed vs speed: businesses want your data, users want less frictionPersistent identity: proving you’re the same person across visits or devicesState: the saved information attached to you, such as baskets, preferences and purchase historyAttribution and accountability: knowing who posted, purchased or interactedAccount fatigue: the frustration caused by low-value services demanding high-effort sign-upWalled gardens: big tech identity systems that simplify things while increasing dependencySelf-sovereign identity: a model where users control their own credentials and accessExamples discussed:Electric vehicle charging appsCoffee shop loyalty schemesAmazon and frictionless checkoutIndependent bookshops and analogue orderingGuest checkout versus full account creationHouse buying and repeated identity verificationSmart home devices that require accountsLocal newspaper paywallsRecipe websites and corporate brochure downloadsGoogle, Apple and Facebook sign-in systemsTimestamps00:00 Introduction: username and password fatigue00:27 Nick’s frustration with electric car charging apps and endless account creation02:40 Peter introduces the “greed versus speed” tension behind digital accounts03:28 Data harvesting, free products and the business model behind sign-ups04:17 Why convenience often pushes people towards platforms like Amazon05:03 Chris questions whether personal data is really as valuable as companies claim07:14 Nick explains the legitimate technical reasons accounts exist: identity, state and accountability10:39 Why digital life makes account creation feel more frequent and intrusive11:32 Chris compares digital sign-ups with older, more human forms of transaction12:56 The independent bookshop as an analogue alternative14:15 Identity and authentication in the physical world15:32 Online purchasing as self-service bureaucracy16:18 Peter points out that non-digital bureaucracy can be just as bad, especially when buying a house17:14 The appeal of a reusable digital identity18:03 Why fragmented identity systems are inefficient and frustrating19:46 Nick presents the “new account nuisance matrix”20:19 Good accounts versus pointless accounts23:25 The worst part of the Internet: sign-up demands for low-value services24:42 Electric car charging as a prime example of unnecessary account friction25:21 Peter begins discussing solutions and warns against false promises from big tech26:18 The dangers of relying on Google, Apple or governments to own digital identity28:02 Why centralised identity systems create security risks28:48 Self-sovereign identity as a possible solution29:26 OutroContactIf there’s a topic you’d like the team to cover, email: [email protected]

In this episode, Fraser McGruer, Nick Hare, Peter Coghill and Chris Wragg explore one of the most enduring pieces of technical advice: have you tried turning it off and on again?What begins with a glitchy video call and a reluctant router reboot quickly develops into a wide-ranging discussion about systems, states and the surprisingly deep logic behind rebooting—not just in computers, but in societies, economies and even our own lives.The team unpack what actually happens when you power cycle a device, from memory leaks and zombie processes to cosmic rays flipping bits in memory. From there, they build a broader framework: what counts as a “state”, what a “good state” might be, and when a system can—or cannot—be reset.Peter introduces a theory of rebootability, with criteria including whether a system has an external reference point, whether it depends on consensus, and whether it can be restarted from outside itself. These ideas are applied to everything from national constitutions and financial systems to climate change and rainforest collapse.Along the way, the conversation touches on revolutions, failed societal resets, post-war reconstruction, and the limits of trying to “go back” to a supposedly better past. The episode closes with personal reflections on resets—from Covid lockdowns to life-changing career shifts and the everyday reboot of sleep.In this episode:Why turning something off and on again actually worksWhat a “state” is (and why it matters)The concept of a “known good state”Peter’s theory of rebootabilitySystems that can’t be reset (climate, ecosystems, global economy)The role of consensus in rebooting social systemsWhy revolutions and resets often failThe appeal of starting over—from software to psychologyPersonal and societal examples of “reboots”Key ideas and concepts:State: The internal condition of a system that determines how it responds to inputsKnown good state: A reliable baseline you can return toRebootability: Whether a system can be reset to a functioning stateBootstrap problem: A system often needs something external to restart itPath dependency / hysteresis: How the past shapes what’s possible nowConsensus vs reality: Some systems only work if people agree they workTipping points: States from which recovery is difficult or impossibleExamples discussed:Routers, computers and memory leaksChess, board games and “soft locks”The climate and rainforest collapseWritten constitutions as “system blueprints”Currency resets (e.g. post-war Germany)The French Revolution and failed systemic resetsPost-war Germany and Japan vs Iraq and AfghanistanReligious and mythological “reboots” (e.g. the Flood narrative)Sleep as a daily biological reboot

In this episode, we explore a deceptively simple question: what makes a death culturally significant?The conversation begins with an unsatisfying Reddit-style list of famous deaths by decade and quickly turns into a more analytical discussion. The team teases apart different kinds of significance: the death of an already important person, the death of someone whose future mattered as much as their past, and deaths that became historically or culturally transformative even when the individual was not especially well known.Along the way, they discuss deaths that mark the end of an era, deaths that act as catalysts for social or political change, and deaths that become mythologised through mourning, media and time. They also consider whether cultural significance can be measured at all, and toy with building a rough model comparing the significance of a person’s life with the significance of their death.Examples range from Princess Diana, JFK and Julius Caesar to George Floyd, Mohamed Bouazizi, Emmett Till and Jesus, with stops along the way for Harambe, Queen Victoria, Archduke Franz Ferdinand and Alan Turing.The episode closes on a more personal note, as each speaker reflects on a death that feels significant to them personally, from Ray Charles to John Cazale and Alan Turing, before things take an irreverent turn in classic Cognitive Engineering fashion.In this episode:What counts as a culturally significant deathThe difference between a significant life and a significant deathDeaths that changed history versus deaths that symbolised lost potentialWhether cultural significance can be measuredWhy time, myth and collective mourning matterPersonal reflections on deaths that still resonatePeople and examples mentioned:Queen Victoria, Vladimir Lenin, John Lennon, Princess Diana, Elvis Presley, John F. Kennedy, Buddy Holly, Ritchie Valens, the Big Bopper, Queen Elizabeth II, Nelson Mandela, Fidel Castro, Michael Jackson, George Floyd, Archduke Franz Ferdinand, Kurt Cobain, Amy Winehouse, Jimi Hendrix, Harambe, Mohamed Bouazizi, Kitty Genovese, Emmett Till, Neda Agha-Soltan, Rachel Corrie, Thích Quảng Đức, the Princes in the Tower, William of Norwich, Crispus Attucks, Julius Caesar, Adolf Hitler, Martin Luther King Jr, Jeffrey Epstein, Ray Charles, John Cazale, John Candy and Alan Turing.

Where did all the eccentric inventors go? The men (and women) in sheds, the gadgets with flashing lights, the sense that the future was arriving one bizarre prototype at a time. In this episode of the Cognitive Engineering Podcast, the panel ask whether invention has become boring — or whether our idea of invention is simply out of date.Starting with Tomorrow’s World, the Innovations catalogue and the golden age of gadgetry, the conversation moves into patents, capital intensity, incremental progress and the shift from lone inventors to teams, firms and platforms. Along the way, the hosts explore whether innovation has moved from atoms to bits, whether low-hanging fruit has already been picked, and why we might be surrounded by astonishing technology while feeling less excited than ever.The episode closes with personal “inventions”, disappointing gadgets, and a reminder that creativity may be more democratised now than at any point in history — even if it no longer looks like a bearded professor wheeling something dangerous into a TV studio.Topics coveredTomorrow’s World, gadgets and the romance of inventionThe myth of the lone inventorAtoms vs bits: physical invention and softwareWhat patent data actually shows about innovationCapital intensity and “low-hanging fruit”Incremental vs breakthrough innovationWhy batteries and concrete are more exciting than they soundDemocratisation of invention: GitHub, maker spaces and 3D printingFalling costs and the invisibility of progressWhy technology might feel boring despite being extraordinaryKey ideas & momentsThe heyday of individual inventors may have been the 19th century, not the 1980sMost inventions today are still physical — just less visibleIncremental progress can be transformative without being dramaticCheap, abundant technology dulls our sense of wonderWhy invention may be everywhere, but invention stories are disappearingFraser’s dual-glasses “optical breakthrough” (and its controversial reception)ContributorsFraser McGruerNick HarePeter CoghillAbout the podcastThe Cognitive Engineering Podcast explores decision-making, technology, creativity and complex systems through thoughtful, wide-ranging conversations. New episodes are released every week or two.LinksFor more information on Aleph Insights visit our website https://alephinsights.com or to get in touch about our podcast email [email protected] few things we mentioned in this podcast:- The Innovations Catalogue http://news.bbc.co.uk/1/hi/uk/2957409.stm- Decline of the Independent Inventor https://www.nber.org/system/files/working_papers/w11654/w11654.pdf?utm_source=chatgpt.com- The ‘bungling inventor’ trope https://tvtropes.org/pmwiki/pmwiki.php/Main/BunglingInventor