No Return: Beyond Transactions in Code and Life
summary
Argues that modeling workflows as atomic return-value transactions breeds brittle systems and life choices, calling this the transactional fallacy. Shows concrete failures: split web forms losing sessions, hidden inter-service state passed via browsers, and the universal spinning beach ball symptom. Proposes a narrative perspective and concrete tools: actor-style streaming or batching, event sourcing and temporal modeling, saga patterns with compensating actions, observability-first design, circuit breakers and supervisor hierarchies for resilience.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:55OBJECT-ORIENTED PROGRAMMING
- 3:11RETURN VALUES
- 3:32The Messaging Myth
- 3:52TRANSACTIONS
- 5:32THE TRANSACTIONAL FALLACY
- 6:07PROGRAMMING IS APPLIED PHILOSOPHY
- 9:31YOUR LIFE IS A NARRATIVE
- 9:53A NARRATIVE HAS A DIRECTION, NOT A GOAL
- 12:39THROW AWAY YOUR FITBIT
- 13:03A NARRATIVE EMBRACES STATE
- 14:08A NARRATIVE FAILS FORWARDS
- 16:02A NARRATIVE IS INTERDEPENDENT
- 18:31Narrative Values
related talks
53mClosing Keynote
54mArchitecture antipatterns and how to beat them 2/2
01h 04mPredictably Unpredictable
02h 59mGroup Cohesion in Transactional Analysis
03mTalks About His Talks
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
48mFault Tolerance on the Cheap Making Systems That Probably Won't Fall Over
51mA Contrarian View of Software Architecture