Code, Calm, and Control Stoicism in Software Engineering
summary
Claims that Stoic practices cut stress, sharpen decisions, and reduce burnout by reframing what developers can control, with trichotomy of control and the classic dichotomy of control as the core model. Concrete techniques shown include negative visualization and doing a premortem before projects. Examples link code quality (in direct control) versus project success (only influence), and historical validation cites James Stockdale surviving seven years as a POW using Stoic methods. Practical, repeatable mental habits replace vague self‑help.
AI-written summary · about
chapters (12)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:22Introduction: Stoicism Meets Software Engineering
- 2:10The Modern Developer’s Challenges & Mental Load
- 5:00The “Storm” of Tools, AI, and Constant Change
- 7:30Control vs. External Pressures Explained
- 10:15What is Stoicism? Core Philosophy Overview
- 13:40Famous Stoics & Their Lessons (Epictetus, Seneca, Marcus Aurelius)
- 17:10The Five Stoic Virtues & Their Meaning
- 20:30Dichotomy vs. Trichotomy of Control
- 23:10Practical Techniques: Negative Visualization & Premortems
- 25:40Applying Stoicism to Daily Engineering Work
- 27:00Final Reflection: Calm, Control & Living a Better Developer Life
related talks
24mModern Stoicism: How practice discipline and stay calm during the crisis
05mSpacetime Management: Lessons from the Stoics
05mSpacetime Management: Lessons from the Stoics
22mHow Stoic Perspective Empowers Agile Leadership
28mStoic Philosophy and Automation Testing
45mEgo-less Programming: the Philosophy of Better Code
01h 29mSolid Code, Solid Life: Clean Code for Your Life
47mModern Mindfulness Techniques for Coders and Other Knowledge Workers