Jeffrey Way posted a poll today that hit a nerve.

91.6% said yes. That's not a poll result — that's a census.

The feeling is hard to name. It's not burnout. It's not impostor syndrome. It's not fear of job loss. It's something weirder: the tools are better than ever, the possibilities are genuinely infinite, and yet something fundamental feels hollow. You can build anything you want, and the "anything" part is somehow the problem.

I've been thinking about why, and the best framework I've found for it is 2,000 years old.

The Real Alexander Story

There's a famous quote: "Alexander wept, for there were no more worlds to conquer." You've probably heard it. Hans Gruber says a version of it in Die Hard: "And when Alexander saw the breadth of his domain, he wept — for there were no more worlds to conquer. Benefits of a classical education."

The irony is that Hans Gruber — a fictional German terrorist trying to sound cultured — got the quote exactly backwards. And so does everyone who repeats it.

The actual source is Plutarch's essay De Tranquillitate Animi ("On the Tranquility of the Mind"), Section 4, written around 100 AD. Here's what Plutarch actually wrote:

Alexander wept when he heard Anaxarchus discourse about an infinite number of worlds, and when his friends inquired what ailed him, "Is it not worthy of tears," he said, "that, when the number of worlds is infinite, we have not yet become lords of a single one?"

The meaning is inverted. Alexander isn't sad because he ran out of things to conquer. He's crushed by how small his achievements are against infinity. He conquered most of the known world and it still wasn't enough — not because nothing was left, but because everything was.

The misquote has its own history. Henry Constable reversed it in a 1592 sonnet — Alexander "wept, lest he should leave no Kingdom unto him for to subdue." Jonathan Swift wrote in 1708 that he'd "read in a certain Author, that Alexander wept because he had no more worlds to conquer" — without citing where. Byron cemented it in The Age of Bronze (1823): "He wept for worlds to conquer." And then Die Hard made it permanently famous.

But the real version is the one that's relevant now.

Plutarch's Essay (And Why It Matters Here)

The essay is structured as a letter to Plutarch's friend Paccius — a successful, prominent public figure who had achieved a lot and was miserable anyway. Sound familiar.

Paccius wanted practical advice on how to not feel like shit despite having everything going for him. Plutarch's answer is surprisingly systematic and, read through the lens of 2026, uncomfortably specific.

The Core Thesis

Plutarch's central metaphor: the source and fountain of all tranquility is in ourselves. We should cleanse and purify that spring, so that all outward and casual occurrences may be made agreeable unto us.

He compares the disordered soul to a fever:

When we are in a fever, everything we eat and drink seems bitter and unpleasant; but when we see others not refusing the same food, we no longer blame the food and drink, but the sickness and the disease within ourselves.

The same circumstances that torment one person are perfectly tolerable to another. Which means the problem isn't the circumstances. It's the disposition brought to them.

What He Rejected First

Before offering advice, Plutarch dismantles the obvious answer. Democritus had said: just do less. Withdraw from public life. Reduce your engagements. Plutarch calls this buying tranquility at the price of inactivity — like telling a sick person to just lie still in bed.

His counterexample is Achilles, sitting idle by the ships during the Trojan War, "wasting away his heart." Withdrawal didn't make Achilles tranquil — it made him more miserable than fighting ever did.

This matters because "just touch grass" is the 2026 version of Democritus's advice, and it doesn't work for the same reason it didn't work then. If you're wired to build, not building makes it worse.

The Prescriptions, Translated for 2026

Plutarch gives five practical prescriptions. Each one maps onto the developer experience in the AI age with alarming precision.

1. Match Your Work to Your Nature, Not Your Ambition

Plutarch uses the tyrant Dionysius as his cautionary example — a man who held supreme political power over Syracuse but couldn't tolerate being second-rate as a poet. He entered his tragedies in competitions, raged when they were mocked, and reportedly sent people to prison over bad reviews. He had everything and was miserable because he was competing in a domain that wasn't his.

The 2026 version: Stop building things because you can and start building things because you should. AI collapsed the cost of building to near-zero, which means the old filter — "is this technically feasible for me?" — is gone. That filter used to do a lot of hidden work. It quietly killed 80% of your ideas before they consumed your energy. Now every idea survives triage. The new filter has to be intentional and internal: does this thing actually matter to me, or does it just scratch the itch of making something exist?

2. Stop Comparing Upward

This is one of the essay's most memorable passages. Plutarch describes an infinite chain of envy:

Those in prison consider those who have been released fortunate; the released envy the freeborn; the freeborn envy citizens; citizens envy the wealthy; the wealthy envy governors; governors envy kings; and kings envy the gods — scarcely stopping short of desiring the power to produce thunder and lightning.

No matter where you stand, there is always someone above you. The ladder has no top rung.

The 2026 version: Get off the timeline. Someone always shipped faster, got more stars, raised more money, had a cleaner architecture. And now the comparison isn't even with other humans — it's with AI itself. "Claude could have written this in 30 seconds, why did I spend a week?" The ladder now has infinite rungs and the rungs are moving. The only sane response is to stop climbing it entirely.

3. Blend the Good with the Bad Consciously

Plutarch compares life to wine mixed with water (as was the Greek custom). The wise person focuses on the wine, not the water. He argues against the tendency to possess ten good things and fixate entirely on the one bad thing.

The 2026 version: Keep a build log, not a ship log. The dopamine cycle of side projects is: idea → excitement → build → ship → brief high → emptiness → next idea. The "blending" Plutarch talks about means deliberately noticing what was good about the process, not just the launch. What did you learn about state machines while building that thing? What did the research teach you about how knowledge actually compresses? That stuff compounds. The shipped artifact often doesn't.

4. Changing Circumstances Doesn't Fix the Mind

This is the fever metaphor above, applied broadly. Plutarch also uses a house metaphor: if you move to a new house but bring all your old furniture — your vices, anxieties, false beliefs — you haven't actually changed anything.

The 2026 version: A new stack won't fix it. A new project won't fix it. AI won't fix it. This is the hardest prescription because it applies so perfectly. If you're in the fever, Rust tastes bitter. Then you try Dart and Dart tastes bitter. Then you try Zig and Zig tastes bitter. It's not the languages. It's not the frameworks. It's not even the projects. The restlessness is the fever, and starting something new is just tasting a different food with the same sick tongue.

5. Stay Engaged, But Wisely

Plutarch's whole point was that withdrawal doesn't work — Achilles sulking by the ships was more miserable than Achilles fighting. But he also didn't advocate mindless busyness. He compares life to loading a ship: too little cargo and it tosses in every wave. Too much and it sinks.

The 2026 version: Don't quit building — quit building compulsively. The difference between intention and compulsion: intention means you chose this project because it aligns with something you care about. Compulsion means you started it at 11pm because the silence was uncomfortable.

The Problem Plutarch Didn't Have

There's one thing the essay doesn't cover, because it couldn't.

The old version of programming had a built-in tranquility mechanism — the deep focus state of solving a hard problem. Flow state. Csikszentmihalyi documented it in 1990: flow requires a balance between skill and challenge, with clear goals and immediate feedback. That was the fountain. Not the output — the process of concentrated effort toward a hard thing.

AI pair programming is genuinely more productive, but it disrupts that flow. You're managing and reviewing instead of thinking and crafting. The thing that used to produce euthymia as a side effect — the actual act of building — now produces less of it per hour spent.

The research backs this up. Norton, Mochon, and Ariely documented the "IKEA effect" in 2012: people value things more when they've invested effort in creating them. Reduce the effort and you reduce the perceived meaning of the output. When Claude writes the function in 30 seconds, it works fine, but something in the maker's relationship to the thing is different. It's not worse code. It's less yours.

Barry Schwartz's paradox of choice research maps here too. The famous Iyengar and Lepper jam study (2000) showed that presenting people with 24 varieties instead of 6 made them dramatically less likely to buy anything. More options produced less satisfaction, more regret, more paralysis. AI doesn't just add more varieties of jam — it adds infinite varieties and then offers to make the jam for you.

Kierkegaard called anxiety "the dizziness of freedom." Frankl warned that freedom without responsibility produces the existential vacuum. When all options are open but none carry inherent weight, the result isn't liberation — it's vertigo.

Kent Beck — the TDD and Extreme Programming guy — wrote about this in 2024. He described a process of grief and adaptation, explicitly using language about identity: "I am not my code." His framing was ultimately optimistic (identity shifts to taste, judgment, architecture), but he validated the grief as real and legitimate.

The Inverted Alexander

Here's the thing about the real Alexander quote versus the fake one.

The Die Hard version — "no more worlds to conquer" — describes a problem of scarcity. You ran out of things. You're done. This is the developer crisis that isn't happening.

The Plutarch version — "the number of worlds is infinite, and we have not yet become lords of a single one" — describes a problem of abundance. Everything is possible, and that makes each individual possibility feel small.

That's the one that 91.6% of Jeffrey Way's followers recognized.

Plutarch's answer is the same one it's always been. The fountain is inside. No tool — not even one that lets you build anything — can clean it for you. The infinite worlds are real, and the feeling of smallness before them is the correct response. The mistake isn't feeling it. The mistake is thinking the next project, the next framework, the next feature will be the one that makes it stop.

It won't. It never does. Alexander tried, and he had armies.

The move is smaller and harder: choose one world. Not because it's the best one. Not because AI picked it for you. Because you decided it matters.

The Plutarch quotes are from W.C. Helmbold's Loeb Classical Library translation and Philemon Holland's 1603 translation of De Tranquillitate Animi (Moralia, Volume VI). The misquote transmission history draws on Anthony Madrid's "And Alexander Wept" (The Paris Review, 2020) and the "Worlds Unconquered" essay at Aptaverse.