Engineering Reality: Lessons from Life, Architecture, and Artifice
summary
Stories link magic and engineering with concrete claims and artifacts: levitated a train ticket in 1997 to illustrate expectation bias and psychological invisibility; taught himself on an Apple IIgs using BASIC and joined the NSFNET pilot in Green River, Wyoming; landed a software job after performing at TGI Fridays and now publishes "Mastering Software Architecture." Practical demos include a custom deck that filled the auditorium with sixes of clubs (only one playable face), a lesson against over‑engineering and for valuing simple, resilient solutions.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 1:37Magic and childhood passions
- 7:01Magician and software architect duality
- 15:41Breaking siloed knowledge myths
- 22:40First tech job and unexpected connections
- 29:22Live audience interaction and astonishment
- 34:03Synergy and range in problem solving
- 41:24Trade-offs in magic and software
- 46:26Familiarity breeds contempt
- 51:43Value of established ideas
- 58:14Over-engineering pitfalls
- 1:00:22Simple solutions and closing thoughts
related talks
35mCraft, Engineering, and the Essence of Programming
45mTaking Back "Software Engineering"
48mEngineering You
58mIs Software Engineering Still an Oxymoron?
01h 00mEngineering Software
56mEssential Architectural Thinking – Why, What, How, When and How Much?
08mLightning talks – 101 Things Software Never Learnt
42mWhat our Brains can Teach us About Software Engineering