Keynote: A Sailor's View of Python And the idea of "Defensive Programming"
summary
Argues that reliable Python systems need explicit design envelopes, detection, and practiced recovery not vague best practices, citing a midnight diesel leak smelled then traced, failed rescue-tape patch, and a decision to limp to Stuart Florida; recommends concrete tools and habits like mypy and pytest, logging/alerts, and CLI recovery scripts so components recombine for jury-rigging recovery rather than mysterious monoliths or silent failures.
AI-written summary · about
chapters (15)
- 0:00DevOps to sailing adventures
- 1:51400-mile sail from Nassau
- 5:45Python and sailboat parallels
- 8:18Boat wear and software threats
- 10:48Defense in systems
- 13:41Design envelope in sailing and code
- 18:58Midnight diesel emergency detection
- 20:48Python lessons from boat design
- 28:18Edge failure scenarios
- 32:49Code smells detection
- 35:58Logging and decisions in crises
- 36:20CLI tools importance
- 39:18Bugs always existed
- 40:42Jury-rigging in software
- 42:30Degraded mode failover
related talks
43mThursday Keynote -- What Programming is Really About
01h 12mKeynote: "Am I A Good Programmer?"
50mKeynote: The naïve programmer
01h 04mKeynote: Learn Programming, then Learn how to Be a Programmer
23mDefensive Programming: The Best Software Development Methodology Ever Invented
01h 00mKeynote: Designed for Education: A Python Solution
40mThe Best Programmer I Know
49mScars, Bruises and Breaks — Programming in Retrospect