Keynote: The Future of Software
summary
Forty years of examples argue that trust fails at the seams: a Cold War 50 baud mannequin setup proves humans track eyes, Boeing’s 737 Max uses MCAS single-sensor logic written to spec by low‑cost contractors and triggers repeated rudder overrides, Air France crashes tie to frozen P2 pitot tubes, and operators must reboot an A380 from the cargo hold. Corporations build Dojo ($1B) and put $0.5B of GPUs on a barge to evade rules, while Borg→Kubernetes collapses app logic to ~5% of stack, making identity and certification the practical chokepoints.
AI-written summary · about
chapters (10)
- 0:00Introduction and early computing
- 2:54Software ubiquity and trust issues
- 7:10Boeing 737 Max software failures
- 11:24Air France 447 and system complexity
- 15:01Evolution of software abstraction layers
- 20:43AI as the next abstraction layer
- 24:15Ethics and regulation in software
- 30:24Cybersecurity and ransomware challenges
- 33:15AI productivity and future of engineering
- 35:22Identity and trust in software
related talks
55mKeynote: The dangers of probably-working software
45mKEYNOTE Are programmers heading towards another bursting bubble?
58mKeynote: What Got Us Here Wont Get Us There
56mKeynote: Defining and Embracing The Software Fragility
52mKEYNOTE 1: The Future, The Past, and … Wait, Where the Hell are We Now?
01h 13mKeynote: The Hidden Architecture of our Time: Why This Internet Worked, How We Could Lose It...
10mKeynote: Make Infrastructure Relevant to A Better Future
59mKeynote