Reading Notes: Meditations, Ego Is the Enemy, Quiet, and Breath Work
How diving deep into stoicism, ego detachment, introversion, and physical self-regulation transformed my engineering leadership and technical execution.
Early in an engineering career, you assume that becoming a better technical leader is strictly a function of learning more programming languages, mastering compiler internals, or memorizing system design patterns.
Over time, you realize that while technical depth is the baseline, what actually determines the trajectory of your systems and teams is your capacity for focus, emotional resilience, and calm decision-making under pressure.
Looking back at my reading stack from late 2023 into 2024, a distinct cluster of non-technical books fundamentally shifted how I approach software architecture, high-stress production incidents, and engineering team leadership.
1. Stoic Equanimity: Meditations by Marcus Aurelius
When an urgent production incident occurs (a broken build pipeline, a sudden App Store rejection, or an unexpected database spike), the natural human response is adrenaline, urgency, and frantic action.
Marcus Aureliusā€™s private journal serves as a timeless reminder of the dichotomy of control: separating what is in our direct control (our reaction, our focus, our thoroughness) from what is outside our control (the unexpected external bug, the market shift, the platform change).
In engineering practice, stoic principles translate into a practical operational discipline:
- Blameless post-mortems: Focusing relentlessly on structural failure modes in the system rather than assigning personal blame.
- Calm incident triage: Resisting the urge to apply hasty, unverified hotfixes that introduce two new bugs for every one they resolve.
- Detached problem analysis: Viewing code as an objective artifact rather than a personal possession.
2. Code Without Identity: Ego Is the Enemy by Ryan Holiday
One of the most insidious blockers of engineering quality is ego. When an engineer links their self-worth to their pull request or architectural proposal, every critique in code review feels like a personal attack.
Ryan Holidayā€™s Ego Is the Enemy lays out the antidote: radical humility, continuous student mentality, and detachment from applause.
Adopting this mindset inside our engineering team completely transformed our code review culture:
- Strong opinions, loosely held: We present architectural trade-offs with explicit risks and alternatives rather than defending a pet solution at all costs.
- Welcoming refactoring: If junior engineers or automated tools find a cleaner, simpler way to implement our logic, we celebrate the simplification rather than protecting legacy lines of code.
- Celebrating deleted code: Measuring productivity by how much unnecessary complexity we remove from the codebase, not how many lines of code we add.
3. Protecting the Solitary Craftsman: Quiet by Susan Cain
Tech culture often glorifies extroverted brainstorming sessions, constant open-plan chatter, and rapid-fire meetings. In Quiet, Susan Cain presents compelling evidence that deep creative breakthroughs, complex architectural synthesis, and deep bug hunting require prolonged, uninterrupted solitude.
Software engineering is fundamentally an act of deep cognitive modeling. You cannot hold a 15-module dependency graph in your working memory if you are interrupted by a Slack notification every seven minutes.
To support this in practice:
- We instituted Focus Blocks: four-hour daily windows where all meetings are prohibited and asynchronous communication is respected.
- We transitioned architectural decision-making from loud verbal meetings to written Request for Comments (RFC) documents, giving introverted and contemplative engineers equal space to evaluate designs deeply.
4. Physiology and Focus: Science of Breath and The Oxygen Advantage
High-performance cognitive work is a biological endeavor. When your body is under chronic stress, shallow mouth-breathing activates the sympathetic nervous system, triggering brain fog and reactive decision-making.
Studying Science of Breath by Swami Rama and The Oxygen Advantage by Patrick McKeown introduced me to the practical mechanics of respiratory regulation and nasal breathing:
- Box Breathing (4-4-4-4): Practicing four-second box breathing before joining critical stakeholder meetings or debugging high-severity outages to immediately lower heart rate and restore executive function.
- Nasal Breathing During Deep Work: Maintaining steady diaphragmatic breathing during programming sprints to prevent screen apnea and sustain mental clarity across hours of intense focus.
The Synthesis
Engineering excellence is not just about writing clean Swift or building scalable backend distributed systems. It is about building an internal operating system that remains grounded, clear, and humble regardless of external noise.
When you cultivate emotional detachment, protect deep solitude, and regulate your nervous system, your technical decisions become sharper, your code becomes simpler, and your leadership becomes a steady anchor for your team.