Split View: 마르쿠스 아우렐리우스의 코드 리뷰: 스토아 철학으로 개발자 멘탈 다스리기

Marcus Aurelius Gives a Code Review: Stoic Philosophy for Developer Mental Health

• The Emperor's Private Journal
• What Stoicism Actually Is
• Epictetus and the Dichotomy of Control
• Memento Mori: Remember Death
• Amor Fati: Love of Fate
• Seneca and the Currency of Time
• The Three Stoic Disciplines
  • Discipline of Assent (Judgment)
  • Discipline of Action (Impulse)
  • Discipline of Desire (Wanting and Avoiding)
• Stoicism and Imposter Syndrome
• Practical Stoicism for Developers
• Stoic Journal Template for Developers
  • Morning Journal (5 minutes before starting work)
  • Evening Journal (5 minutes after finishing work)
• Burnout and Stoic Philosophy
• Closing: The Emperor's Last Word
• Practice Quiz: Stoic Developer Scenarios
• References

The Emperor's Private Journal

Somewhere around 170 CE, the most powerful man in the Western world was having a bad day.

Marcus Aurelius Antoninus — emperor of Rome, commander of 400,000 legionaries, administrator of the largest empire in history — was also dealing with plague, German invasions, financial crises, and political backstabbing. Not so different from a bad sprint, really.

Every night, he wrote in a private journal. In Greek, not Latin — Greek was the philosopher's language, the language of rigorous thought. He wrote it for no one but himself. The title: Τὰ εἰς ἑαυτόν — To Himself. What we call the Meditations.

The remarkable thing about reading the Meditations today is how immediately applicable it feels. Change a few nouns, and Marcus could be a senior engineer writing performance review season reflections.

"Confine yourself to the present." — Meditations VIII.7

If that's not a prompt for closing your Slack notifications and actually fixing the bug, I don't know what is.

What Stoicism Actually Is

Stoicism was founded in Athens around 300 BCE by Zeno of Citium, who taught in the Stoa Poikilē — the painted porch — giving the school its name. It spread to Rome and produced three towering figures: Marcus Aurelius (emperor), Seneca (statesman and playwright), and Epictetus (former slave).

The central claim of Stoicism is elegant and radical: External events do not disturb us. Our judgments about external events disturb us.

As Marcus puts it: "If you are distressed by anything external, the pain is not due to the thing itself, but to your estimate of it; and this you have the power to revoke at any moment." — Meditations VIII.47

This is not passivity. This is a precise claim about where the work of a good life actually happens: inside, not outside.

Epictetus and the Dichotomy of Control

The most practically useful concept in Stoicism belongs to Epictetus, the former slave. His Handbook (Enchiridion) opens with a distinction that, once you've seen it, you cannot unsee:

"Τῶν ὄντων τὰ μέν ἐστιν ἐφ' ἡμῖν, τὰ δὲ οὐκ ἐφ' ἡμῖν." (Of existing things, some are in our power and some are not in our power.) — Epictetus, Enchiridion 1.1

In our power: our judgments, impulses, desires, aversions — our inner mental activity. Not in our power: our bodies, reputations, property, other people's actions.

Applied to developer life:

The Stoic prescription: invest your energy in the left column. Accept, without distress, whatever happens in the right column. This doesn't mean not caring — it means not allowing outcomes you can't control to determine your inner state.

Memento Mori: Remember Death

The most counterintuitive Stoic practice:

Memento mori — remember that you will die.

In modern ears this sounds morbid. To the Stoics it was liberating. When you hold your own death in view, the code review that seemed devastating this morning suddenly shrinks to its actual size. The promotion you didn't get, the architectural argument you lost, the product that got cancelled — these things are real, but they are not the scale of a human life.

Marcus uses a sharp variant of this practice he calls the view from above: imagine observing your situation from the perspective of the cosmos, or of history. Alexander the Great and his enemies now share the same dust. All the Roman emperors Marcus knew of were gone. He would be gone too.

"Alexander the Great and his mule driver both died and the same thing happened to both." — Meditations VI.24

This is not nihilism. Marcus cared intensely about ruling well. But the cosmic perspective kept the small things from becoming large things. He ran an empire; we run microservices. Neither of us should let a bad code review ruin a week.

Amor Fati: Love of Fate

Friedrich Nietzsche coined the phrase amor fati — love of fate — but the Stoic roots run deep. Marcus expresses it as:

"The impediment to action advances action. What stands in the way becomes the way." — Meditations V.20

This is perhaps the most useful single sentence in Stoic philosophy for software engineers.

The production incident you're dealing with is not an obstacle to doing good work. It is the work. The legacy codebase that seems like punishment is the actual problem your team was hired to solve. The hostile stakeholder who keeps changing requirements is the real-world complexity that separates software engineering from puzzle-solving.

Amor fati doesn't mean pretending bad things are actually good. It means developing the orientation where you meet obstacles as the substance of a meaningful professional life, rather than interruptions to it.

A Stoic framework for incident response:

Step 1 — Discipline of Assent: The moment the alert fires, stop the automatic reaction (panic, self-blame). Acknowledge only the fact: "An incident has occurred."

Step 2 — Discipline of Action: Build a list of controllable actions. Check logs, analyze metrics, open communication channels, assess whether a rollback is possible.

Step 3 — Discipline of Desire: Release the urgency of "this needs to be fixed immediately." Focus not on a perfect resolution, but on the best available action right now.

Step 4 — View from Above in the post-mortem: What does this incident teach us about the system? Viewed from six months out, this may have been the catalyst that made the system more resilient.

Marcus never stopped his evening reflections, even while commanding armies on the Danube frontier against Germanic tribes. No matter how urgent the production fire, five minutes of post-incident notes will make you better prepared for the next one.

Summum bonum — the highest good — in Stoic philosophy is not money, fame, or career success. It is virtue (ἀρετή, arete): the exercise of reason and ethics in every circumstance, regardless of outcome.

Seneca and the Currency of Time

Of all the Stoics, Seneca is the most urgently readable. He wrote letters to a friend named Lucilius that read like the emails a very wise colleague sends at the end of a long day:

"Dum differtur vita transcurrit." (While we delay, life passes.)

And more directly:

"Ita fac, mi Lucili: vindica te tibi." (Do this, my Lucilius: reclaim yourself for yourself.)

Seneca believed that most people spend their lives in a peculiar poverty: they have money, health, and opportunity, but they give their time — their actual lives — to others without a second thought. They're too busy for what matters.

For developers in the attention economy, this lands hard. How many hours last week did you spend in meetings that could have been documents? How many evenings did you spend anxiously refreshing Slack? How much of your attention — the substance of your life — went to the urgent rather than the important?

"Nusquam est qui ubique est." — Seneca, Letters 2.2 (He who is everywhere is nowhere.)

Slack notifications, email, JIRA, GitHub, Confluence, Pagerduty. The engineer who is everywhere is nowhere. Seneca would have had thoughts about this.

The Three Stoic Disciplines

Marcus Aurelius organized his practice around three disciplines, articulated clearly by the later philosopher Epictetus (Robertson, 2019):

Discipline of Assent (Judgment)

Don't react automatically to events. Pause between stimulus and response. The Stoics called the automatic emotional reaction a passion (pathos) and distinguished it from a rational emotion (eupatheia). You can feel frustrated; frustration is information. But the frustration shouldn't drive the response.

Scenario: You receive a request to completely rewrite your PR

Monday morning. On the PR you submitted Friday, a comment reads: "This approach is fundamentally flawed. Please redesign."

Automatic reaction (pathos): I spent three days on this. This person is dismissing my abilities.

Applying the Discipline of Assent:

• Pause. Take your hands off the keyboard.
• Is this factually accurate? Analyze only the technical content of the comment.
• Is this about me or about the code? Notice the word "approach" — it's about the code.
• Is there something to learn from this feedback? Try to understand the alternative the reviewer is suggesting first.

Rational emotion (eupatheia): Disappointing, but this is an opportunity to learn a better design. Let me ask specifically which part is problematic.

Scenario: Your idea gets ignored in a team meeting

During an architecture meeting, your proposed caching strategy gets passed over without a single word of discussion.

Applying the Discipline of Assent:

• Was I ignored, or did time simply run out? Verify the intent before assuming the worst.
• The value of my idea is independent of the team's reaction. If you believe it's a good idea, write it up in Slack or a design document and share it again.
• Focus on the process (did I make a good proposal?) not the outcome (was it adopted?).

Discipline of Action (Impulse)

Act for the common good, but hold the outcomes loosely. In Stoic terms: have preferred indifferents. You should try to write excellent code — that's a reasonable preference. But the specific outcome (merge approval, praise, promotion) is not within your control and should not be the source of your self-worth.

Scenario: Your tech debt proposal gets rejected

You wrote a detailed technical proposal to refactor a legacy module with 20% test coverage. You included a migration plan, cost estimates, and ROI projections. But the product manager says "new features are the priority right now" and defers it to next quarter.

Applying the Discipline of Action:

• Did I make the best proposal I could? If yes, my role is fulfilled.
• The decision belongs to others. The PM may have business context I'm not aware of.
• Focus on what I can control. Even if refactoring is deferred, writing thorough tests for new code is within my control.

Scenario: A third-party outage occurs during your on-call shift

The payment system's external API is down. Orders are failing. Restoring the external service is outside your control.

Applying the Discipline of Action:

• Outside your control: when the external API recovers
• Inside your control: activating fallback mechanisms, communicating status to users, setting up retry queues, sharing situation with the team
• Take the best available action without wasting energy on unproductive regret about past decisions

Discipline of Desire (Wanting and Avoiding)

Desire only what you can control. Fear losing only what you can control. Since reputation, job security, and career advancement are all, ultimately, not fully in your power — the Stoic does not build her identity on them.

Scenario: You don't get promoted

Two of your peers made senior engineer. You got "let's revisit next quarter."

Applying the Discipline of Desire:

• Promotion is outside my control. The decision involves team budgets, organizational structure, timing — variables I don't fully see.
• What is inside my control: technical growth, collaboration skills, acting on feedback. Focus there.
• Comparison is poison. Your peers' promotions are their story. Your growth trajectory is yours alone.

This sounds ascetic. It isn't. Marcus owned great wealth, wielded enormous power, and cared about results. But he held these loosely enough that losing them didn't make him someone else.

Stoicism and Imposter Syndrome

The Meditations reveal something startling: Marcus Aurelius, emperor of Rome, had imposter syndrome.

This is not just a developer problem. When psychologists Pauline Rose Clance and Suzanne Imes first formally described the phenomenon in 1978 (Clance and Imes, 1978), they found high-achieving women attributing their success to luck or others' mistakes. Subsequent research suggests approximately 70% of people experience impostor feelings at least once in their lives (Sakulku and Alexander, 2011). In the technology industry, where new frameworks and paradigms emerge constantly and what you don't know is painfully visible, the phenomenon hits especially hard.

Marcus worried constantly about whether he was living up to his philosophy. He berated himself for laziness, for spending too long in bed, for not being as good a person as his Stoic heroes. The most powerful man in the Western world doubted himself in almost exactly the ways junior engineers do.

His response is instructive. He didn't try to eliminate the self-doubt — he redirected his attention. Instead of asking am I good enough? (unanswerable, dependent on external validation), he asked am I doing my best work right now, with the tools I have? (answerable, within his control).

"You have power over your mind, not outside events. Realize this, and you will find strength." — Meditations

Moments when developer imposter syndrome activates:

• When senior engineers use terminology you don't recognize
• When you can't solve an algorithm problem in an interview
• When other team members' PRs seem to pass review on the first try, every time
• When learning a new framework makes you feel like you "don't know the basics"
• When you copy an answer from Stack Overflow

The Stoic reframe:

In every one of these situations, imposter syndrome arises because you've placed your self-worth in the right column of Epictetus's table — the things outside your control. Others' perceptions, comparisons with peers, outcomes at specific moments — all outside your control.

Imposter syndrome is, in Stoic terms, a confusion about which column you're in. You feel inadequate because you're measuring yourself against an external standard (other people's perception of you) rather than an internal one (are you improving, are you honest, are you trying). The Stoic move is to return to what you can actually control.

And remember: Marcus Aurelius himself doubted his own qualifications. Imposter syndrome is not evidence that you are insufficient — it may be a signal that you are growing. People who never leave their comfort zone never experience impostor feelings.

Practical Stoicism for Developers

Morning Premeditation (premeditatio malorum) Five minutes before starting work: what difficulties might I encounter today? A contentious PR review? A confusing requirement? A production alert? Visualize handling each with equanimity. This is not pessimism — it's inoculation.

Evening Review (Seneca's practice) Three questions at day's end:

• What bad habit did I struggle against today?
• What virtue did I practice?
• In what way did I improve?

The Dichotomy Check When stressed: is this in my control, or not? If not, what is the part of this situation that is in my control? Redirect energy there.

The View from Above When a conflict feels all-consuming: what would this look like in a year? In ten years? To a thoughtful observer on the other side of the planet? Scale restores proportion.

Stoic Journal Template for Developers

Seneca had a daily habit of reviewing his day each evening. Marcus practiced premeditatio malorum (negative visualization) each morning. Combining these two practices, here is a Stoic journal template designed for developers.

Morning Journal (5 minutes before starting work)

## Date: \_\_\_\_

### 1. Premeditatio malorum (Negative Visualization)

Three worst-case scenarios that could happen today:

- (e.g., My PR could be entirely rejected)
- (e.g., A production incident could occur)
- (e.g., Requirements could change completely)

### 2. Control Dichotomy

Among today's stressors:

- In my control: (e.g., code quality, communication attitude)
- Outside my control: (e.g., merge decisions, teammates' moods)

### 3. One Virtue to Practice Today

- (e.g., Patience - I will not respond defensively to code reviews)

Evening Journal (5 minutes after finishing work)

### 1. Seneca's Three Questions

- Bad habit I corrected today: (e.g., didn't multitask during meetings)
- Virtue I practiced: (e.g., answered a junior's question thoroughly)
- Way I improved: (e.g., learned a new error handling pattern)

### 2. Discipline of Assent Review

Was there a moment I reacted emotionally today?

- Situation: (e.g., received a sharp message on Slack)
- Automatic reaction (pathos): (e.g., anger, defensiveness)
- Rational reframe (eupatheia): (e.g., the other person may have been stressed too)

### 3. Note for Tomorrow

- (e.g., Draft the tech debt issue first thing tomorrow morning)

You don't need to write this every day. Marcus Aurelius didn't write every day either. But on particularly hard days — after a production incident, after an emotionally charged code review, when burnout signals are flashing — five minutes of reflection makes a remarkable difference.

Burnout and Stoic Philosophy

Developer burnout is not simply overwork. The World Health Organization defines burnout as "a syndrome resulting from chronic workplace stress that has not been successfully managed." Its three dimensions are: (1) energy depletion or exhaustion, (2) increased mental distance from or cynicism about one's job, and (3) reduced professional efficacy.

Analyzed through the lens of Stoic philosophy, burnout maps precisely onto failures of the three disciplines:

1. Failure of the Discipline of Assent leads to Exhaustion

When you interpret every piece of feedback as a personal attack, blame yourself for every incident, and judge every requirement change as irrational — emotional energy depletes rapidly. Without the Discipline of Assent, a single Slack message can drain your reserves for the day.

2. Failure of the Discipline of Action leads to Cynicism

When you fixate on outcomes you cannot control, learned helplessness sets in. "No matter how good the code is, the requirements will change." "No point suggesting anything, nobody listens." This cynicism emerges because you've staked your sense of agency on outcomes outside your control. The Discipline of Action teaches us to find intrinsic satisfaction in the quality of effort, independent of results.

3. Failure of the Discipline of Desire leads to Reduced Efficacy

When you crave promotion, recognition, or perfect code — things outside your control — achievement never satisfies, and failure devastates. The Discipline of Desire asks you to measure efficacy by internal standards: Did I do my best today? Was I honest? Did I learn something?

A Stoic approach to burnout recovery:

• Setting boundaries is a virtue. In Stoic philosophy, justice is a cardinal virtue. If you are not just toward yourself, you cannot be just toward others. Declining overtime is not weakness — it is self-preservation, and it is a long-term application of the Discipline of Action for your team and organization.
• "No" is a complete sentence. As Seneca wrote, he who is everywhere is nowhere. Saying "yes" to every request is not a virtue — it is a dissipation of attention.
• Recovery is not laziness. Marcus chastised himself for lingering in bed, but he also wrote about respecting the rhythms of nature. Adequate rest is a precondition for the sustainable practice of virtue.

Closing: The Emperor's Last Word

Marcus Aurelius died in 180 CE, campaigning on the Danube frontier. He never published the Meditations. It was never meant for us. It was a private training regimen — a man who happened to be running the world, reminding himself daily of principles he kept forgetting under pressure.

"The first rule is to keep an untroubled spirit. The second is to look things in the face and know them for what they are." — Meditations VIII.7

An untroubled spirit, not because nothing is hard, but because you've located your self-worth somewhere that bad code reviews cannot reach. Looking things in the face, not pretending problems don't exist, but not catastrophizing them either.

The production server will go down. The PR will get rejected. The roadmap will change. The code you were proudest of will be deleted.

And you, like Marcus on the Danube, will write your reflections, return to the work, and choose — one more time — to be someone who meets difficulty with equanimity.

That's the emperor's code review. And it approves your PR.

Practice Quiz: Stoic Developer Scenarios

Read the scenarios below and consider how you would respond using Stoic principles.

References

• Aurelius, M. (c. 170-180 CE). Meditations. Gregory Hays trans. (2002). Modern Library.
• Epictetus (c. 108 CE). Enchiridion. Nick White trans. (1983). Hackett Publishing.
• Seneca, L.A. (c. 65 CE). Letters from a Stoic. Robin Campbell trans. (1969). Penguin.
• Robertson, D. (2019). How to Think Like a Roman Emperor. St. Martin's Press.
• Holiday, R. (2014). The Obstacle Is the Way. Portfolio/Penguin.
• Irvine, W.B. (2008). A Guide to the Good Life: The Ancient Art of Stoic Joy. Oxford University Press.
• Clance, P.R. and Imes, S.A. (1978). The Impostor Phenomenon in High Achieving Women: Dynamics and Therapeutic Intervention. Psychotherapy: Theory, Research and Practice, 15(3), 241-247.
• Sakulku, J. and Alexander, J. (2011). The Impostor Phenomenon. International Journal of Behavioral Science, 6(1), 73-92.