The Dichotomy of Control & Stoicism as Practice

Internalize Epictetus's distinction between what is up to you and what is not — in a form precise enough to apply at 3am, and refined enough to resist the glib version that has poisoned popular Stoicism. Then move from the dichotomy as a frame to Stoicism as a daily working practice, via the 14-day journal. The dichotomy is already operating in your engineering practice. When production fails, you partition instantly: my code, the database, the upstream API, AWS? You don't feel personally responsible for a region outage; you do feel responsible for yesterday's NullPointerException. The diagnostic move — what is the smallest unit of agency I can act on right now? — is the Stoic move. What changes outside engineering is that the boundary doesn't draw itself: no interfaces, no stack traces, and the system you're debugging includes you. Three Stoic technologies map onto disciplines you already run: premeditatio malorum is the pre-mortem (Klein and Kahneman validated it; the Stoics shipped it in the first century); the view from above is the architecture-level zoom — deliberate movement between zoom levels, then back to the tactical problem with proportional weight; the morning-and-evening review is the standup-and-retro pattern applied to a self instead of a team — and if you work solo, it is the retro infrastructure you don't otherwise have.