Be the Moth

Credit flows to the title, not to the hand that did the work — true on the short clock of promo cycles, false on the long clock of who the org says built the thing. Aim to be the moth, consumed by the light of the work itself; come back for the certificate only often enough to earn the leverage that carries you to a bigger flame.

The line that runs corporate life

In the Iliad, and in the film Troy, Achilles' Myrmidons storm the beach and take it before Agamemnon's army has even landed. Agamemnon walks in afterward to claim the victory. When Achilles points out that it was the soldiers who won the battle, Agamemnon gives him the whole thesis of corporate life in five words: "History remembers kings, not soldiers." He'll carve his name in stone across Greece, he says. Achilles tells him his own name is written in sand, for the waves to wash away.

Hold onto that image, because both halves of it are true — just on different clocks. On the short clock, Agamemnon is right: the person with the title collects the credit, and the people who did the work disappear into "the team." On the long clock he is catastrophically wrong, and we'll get there. But the modern org runs on his logic, so it's worth seeing exactly how the king ends up with credit for a beach he never took.

The same story, in a modern key

You've probably heard the smaller, glossier version of this — and it's told as praise for the king. Engineers bring Steve Jobs an iPod prototype and say it can't be made any smaller. Jobs drops it into a fish tank, points at the air bubbles rising out, and says: those are bubbles, so there's empty space in there — make it smaller. It gets passed around as proof of the visionary who saw what his engineers couldn't.

But whatever shrank the iPod was a new 1.8-inch drive and a stack of unglamorous materials and thermal trade-offs — soldiers' work. The fish tank is Agamemnon's version of events, dressed up as a management lesson. And here's the tell: trace the anecdote back and every retelling — Business Insider, Cult of Mac, a thousand LinkedIn posts — points to a single origin, one Quora post by a former Apple engineer. No corroboration, not in the authorized biography. It might have happened. But notice what the story did: the engineer who told it dissolved into it, and Jobs became the hero of an anecdote a soldier narrated.

That is the whole mechanism in miniature. This is legibility beating reality: an organization doesn't remember what happened, it remembers the version that's easy to retell — and the retellable version always rounds toward the most senior name in the room. A story needs one protagonist, and the title is the obvious slot.

Why credit flows to the title

Credit capture in a normal company is almost never theft in the movie sense. Nobody twirls a mustache. It's structural — which is exactly why it's so hard to name and so easy to tolerate. Three forces do the work.

Visibility is asymmetric. Credit gets assigned in rooms — the design review, the calibration meeting, the leadership update, the demo to the director. Seniors and managers live in those rooms; that's most of what their job is. The person who did the work is usually at their desk doing more of it, not in the room narrating it. So the account of the work that reaches the people who allocate reward is almost never delivered by the person who did it. The king stands where history gets written; the soldier stands on the beach. This is The Work Doesn't Speak for Itself stated as geography.

Attribution compresses on the way up, and compression rounds to the king. "Priya found the bug that was corrupting the ledger" becomes "the team fixed the data issue" becomes "under Raj, we closed out the data risk" becomes "Raj drove the reliability win." Every hop upward drops a name, and it rounds toward the most senior person still in the sentence — for the same lazy reason history remembers kings. No one lied at any step. Organizational memory is just a lossy channel, and titles are the bits that survive compression. Hold that thought; later it turns out the level is the unit the compression rounds to, and that changes what you should chase.

The promo packet is the stone the king carves his name into. This is the sharp, concrete one, especially at big companies, where advancement runs on a written case for scope and impact. A senior's evidence of impact frequently is the work of the people below them. The same project becomes "I drove X across the org" in one person's packet and "executed well on X" in another's review. The person who did it can't bank their best work at full value, because it's already been reframed as someone else's leverage. Over a single piece of work, credit is close to zero-sum — the same dynamic as The Labor Illusion and Cookie Licking: Claiming Work Without Doing It: finished work with no story attached is unclaimed territory, and it goes to whoever tells the story first.

The honest complication

If it stopped there this would just be a grievance, and grievances make bad engineers and worse careers. So here's the part you have to hold in the same hand.

The ladder is supposed to reward people for impact through others. Mentoring, setting direction, unblocking, absorbing risk so the people under them can move fast — that is real senior work, and often the load-bearing contribution genuinely was the lead's judgment call while someone else executed it. A person who creates leverage has earned credit for the leverage. That's not corruption; that's the job.

The problem is narrower and meaner than "seniors steal credit." It's that "I created the leverage" and "I harvested the output" look identical on paper. Both read as "drove X across the team." The system has no built-in way to tell the mentor apart from the magpie, so absent any other signal, it rounds to the senior every time — deserved or not.

There is one test that tells them apart, and it's worth carrying: does this person credit you in the rooms you're not in? Credit paid in your absence is real. Credit paid only to your face is theater. And a blunt corollary — when the thing breaks at 3am, whose phone rings? If the credit floated up to the lead but the pager comes down to you, you've found your Briseis: the honor went to the king, the labor stayed with the soldier. Keep this test; you'll need it again at the end, when you have to work out why your own credit went missing.

What Achilles actually did — and what it cost

The Iliad isn't really a poem about a war. Its first word is mēnis — "wrath" — and the wrath is specifically Achilles' rage at his boss taking the prize he earned. The founding text of Western literature is, structurally, a story about credit theft and the retention crisis it triggers. What Achilles does about it is worth studying precisely because it's half brilliant and half ruinous.

He withdrew his labor. Agamemnon confiscates Briseis — not a love interest but the geras, the public token that marks who contributed most — so Achilles stops fighting and sits in his tent. He doesn't argue louder in the meeting. He removes the one input the whole enterprise silently depends on. The insight underneath it is real: while you're doing the work, your value is invisible; it becomes legible only in its absence. No one could see how much Achilles carried until he set it down and the Greeks started losing. That's the shadow side of Too Critical to Promote and Single-Threaded Owner — being load-bearing is leverage, but it's a cage, not a career.

He refused the buyout. This is the move most people forget, and it's the most instructive. As the Greeks collapse, Agamemnon panics and sends an enormous package: Briseis back untouched, plus gold, tripods, horses, seven cities, a daughter in marriage. A life-changing settlement. Achilles says no. His reasoning is the entire point — honor you have to buy back with treasure was never the honor you were owed. You cannot fix a recognition problem with money. A retention bonus does not repair a stolen promotion. He knew the difference between being paid and being credited, and refused to let the first quietly launder the second.

And it cost him everything that mattered. The strike "worked" — Agamemnon caved. But Achilles didn't come back vindicated. He came back because Patroclus, the person closest to him in the world, put on Achilles' armor, went out in his place, and was killed. The leverage Achilles pulled to win his recognition fight is the same act that got the person he loved most killed. By the time Agamemnon returns the prize and half-apologizes ("the gods took my wits"), Achilles no longer cares about it. The credit war had already burned down the thing it was supposed to protect.

So the tactics cut both ways. Withdrawing, refusing to be bought, going over your boss's head — these can win the short-clock fight, and they can incinerate what you were fighting for. Quiet-quitting is Achilles in his tent: it makes your value legible, and it has collateral, and sometimes the collateral is you.

The two clocks

Here is why Troy is the right frame and not just a nice hook: it hands you two verdicts on two different clocks, pointing opposite directions.

On the short clock — the sprint, the quarter, the calibration cycle, the promo round — the king wins. Jobs gets the fish-tank story; the drive engineers are anonymous. The lead gets the packet; the person who did it gets "executed well." Titles win the meeting where reward is handed out, and that meeting is soon.

On the long clock, the soldier wins. For Achilles the long clock ran three thousand years — we still open the poem to the wrath of Achilles, while Agamemnon, King of Kings, is a footnote you have to be reminded about. Yours won't run three thousand years, and it doesn't need to. Your long clock is the span of organizational and professional memory: who people say built the thing two years and three reorgs later, when the title has moved on and the work is still running. That clock is measured in years and careers, not quarters — long enough to compound into reputation, the next role, and the thing people call you when they genuinely need it done.

And the reason the long clock can favor the soldier at all is that the work itself can carry your name — not only through famous inventions. You don't need a named algorithm or a landmark paper. Almost all durable credit is ordinary and organizational:

You're the answer when someone asks "who actually understands billing?"
The migration everyone still refers to by the plan you wrote.
The runbook that's the first link pasted into every incident channel.
The onboarding doc every new hire gets handed on day one.
The design doc still cited in reviews long after you rotated off the team.
The dashboard the whole org checks every morning, that you built.

None of these are world-changing. All of them attach your name to something that outlives the meeting where credit was assigned. That is Achilles' real strategy, translated down to human scale: not "win the argument in the room" but "build the thing the org can't retell its own story without naming you."

The moth and the fly

There's a Sufi fable — narrated by the Qawwal Fariduddin Ayaz, rooted in Attar's Conference of the Birds — that comes at all of this from the opposite direction, and it's the one to set your compass by.

The flies come to the King of the Moths and demand equal standing. We also have wings, we also fly — grant us the status of a moth. The king doesn't argue. He gives them a single task: go find the light. That is the one thing a moth does.

The flies take off and come back in fifteen minutes. They report like surveyors: a lamp over there, a fire here, a funeral pyre in the distance. They saw every light in the village. Then they settled down and waited for the verdict — so, who won? Announce it when the moths get back.

The king says: the decision is already made. The true moths who found the light never came back — because the one who finds the light surrenders to it, flies into it, becomes one with it. It is consumed. Only the ones who wanted a certificate came back to collect it. Those who want a certificate come back.

The moth dies in the flame. That is not the tragedy of the story — it is the proof. The flies survive precisely because they held themselves back; they surveyed the fire instead of entering it. The moth is a moth because it was willing to be consumed by the thing it sought. The fly wanted the name without the fire, and its survival is the evidence that it never earned it.

Now set this against everything above. The Achilles story told you to guard your credit — narrate your work, correct the record, don't let the king carve his name over your beach. The moth story says something that sounds like the opposite: the one who comes back for the certificate reveals they were never really in it. So which is true?

Be the moth — and come back for the certificate

Both are true, and the space between them is where you actually build a career.

Aim to be the moth. Let the work consume you — not for the audience, not for the announced winner, but because the flame is worth flying into. This is the only thing that produces work worth remembering in the first place, and it is the better way to live: to be so far inside a hard problem that you stop performing for anyone watching. The fly's sin was never that it reported back. It's that reporting back was all it did — it surveyed every light and entered none. An engineer who only ever produces the trail (the status update, the visibility, the certificate) and never disappears into the actual problem is a fly, and everyone eventually smells it. That's the failure mode buried in The Work Doesn't Speak for Itself: narration laid over no substance gets found out, and faster than people expect. So default to the light. Be the one who goes quiet for two weeks and comes back with the thing genuinely solved. That is the moth, and the moth is who to be.

But come back for the certificate sometimes — not because the certificate is the point, but because it is leverage, and leverage buys bigger flames. The title, the promotion, the recognized ownership: none of these are the light. They are what gets you access to more light — the harder problem, the larger system, the room where the real fire is burning. A moth with no standing gets handed the small lamps; a moth who came back just often enough to be given a title gets sent to the bonfire. The certificate is not the reward; it is the key to the next flame.

So the discipline the fable can't teach you — because it is a parable about the soul, and you have a career — is the balance: be the moth almost always, and be the fly on purpose, occasionally, without shame. Do the real work for its own sake and let it consume you. Then, on the pieces that matter, come back once, put your name on it, say plainly what you did, bank the standing. And take the leverage that standing bought and fly straight back into the next fire. Claiming your work is not a betrayal of the moth; it is how the moth keeps getting sent toward brighter and brighter light instead of being handed a lamp and forgotten.

Because that is the one thing the fable leaves out, and a company won't. In the story, the moth that is consumed is known to be the true moth — the King of Moths keeps the record. In a company, no king is keeping that record for you. The Achilles who dies gets an Iliad written about him; the engineer who is consumed anonymously by a critical system gets a line in someone else's packet and a shipped product with the company's name on it. So you come back — not to become a fly, but so that when you fly into the flame, someone knows it was you. Be remembered on purpose. Then go be the moth again.

The level is the container credit pours into

There's a deeper reason the certificate matters, and it's worth being precise about — because "leverage for bigger flames" undersells it. Go back to the second force from earlier, the way attribution compresses upward. It doesn't round to a name at random; it rounds to a level. Your org level is the org's pre-computed, legible answer to the question "how much is this person's work worth?", and credit gets poured into that container by default. Two engineers do identical work; the higher-level one is assumed to have done the hard part, and the credit pools around them. Nobody decided to be unfair. Level is simply the cheapest available proxy for contribution, and legibility beating reality guarantees the org will reach for it. This is credit rounding to the title taken to its root: the title isn't merely a rounding target — the level is the unit your work gets denominated in.

The consequence is brutal and clarifying. Below the bar, your good work leaks upward. The same moth-work that would read as "leadership" from someone a level above you reads as "solid execution" from you — and worse, it becomes evidence for the person holding the level above you: "look how well my team executed." You are, structurally, generating credit that pools into someone else's container. At or above the bar, the identical work sticks to you and reads as the senior contribution it always was. This is why early-career narration isn't insecurity — you are fighting a real level tax, a structural leak that no amount of quiet excellence closes on its own.

So the certificate reframes one final time, and this is the sharpest version: it is not a receipt for work you already did — it is the container that makes your future work count as yours. Get the level, and the moth-work that used to leak suddenly adheres. Chasing it, then, is not vanity and not a betrayal of the flame. It is buying the vessel that stops your fire from being credited to someone standing above you. That is a legitimate thing to want, and wanting it hard is not the fly's error — as long as you're still flying into flames while you chase it.

When the moth doesn't get the respect

Being the moth earns respect. But sometimes you do the deep work, you come back for the certificate, and the respect — the promotion, the level, the credit — still doesn't come. This is the moment the fable can't help you with, and it's the moment that breaks people, so it's worth walking through honestly.

First, split "respect" in two, because you almost certainly have more of it than you feel. Peer respect — the engineers who can see depth know exactly who the real moths are; this travels the shadow org chart, and being the moth almost always earns it. Institutional respect — level, promo, comp — is allocated by legibility, not depth. When you feel unrespected, you usually mean you hold the first and lack the second. That's real, and the second is worth pursuing because it's the container from the section above — but naming the split matters, because it tells you you are not actually unrespected. You are craving the lesser respect while already holding the greater one.

Then diagnose why the certificate didn't come, because the fix is completely different for each cause:

You were a silent moth. You did the work and never actually came back for it — no narration, no name on the artifact, no explicit ask. This is the most common case and the most self-inflicted. The fix is the whole "come back for the certificate" discipline above. Do that first, before concluding the org is unfair.
You're below the bar and it leaked. You claimed it, but your level poured the credit into someone else's container. The fix isn't more resentment — it's the explicit promotion conversation: "if I land X, is that the next level?" Get your manager to name the bar and become a pre-committed witness. This is a solvable diagnosis, not an injustice.
You flew into a flame the org can't see. You did genuinely deep work on something the people who allocate reward don't value. Painful, and more narration won't fix it — you have to aim your moth-nature at fires that are both deep and load-bearing to the org. Change the flame, not yourself.
An Agamemnon is harvesting it. A specific person is claiming your work. The credit-in-absentia test from earlier already caught them; the fix is sponsors, skip-levels, and a dated record that routes around the one mouth that profits from your silence.

Now the trap, and it's the one hiding inside your own craving. A moth consumed by wanting the certificate is no longer consumed by the flame — and that is, precisely, the fly's condition. This is the Achilles warning made personal: denied his due, he sat in his tent, and the resentment that replaced the work got Patroclus killed. The danger of being denied respect is not the denial. It's that the craving hollows out the thing that made you worth respecting, and turns the moth into the fly it was better than. Sulking while wanting — craving the outcome while refusing to coldly play for it — is the worst square on the board: you get neither the work nor the certificate, only the bitterness.

So when the respect doesn't come, the honest menu is:

Play for it, coldly and on purpose. If you want the level, run the fly moves without shame — narrate, build sponsors, take visible and load-bearing scope, ask the explicit question. The mistake is never wanting the promotion; it's wanting it passively and resenting its absence.
Change the flame. If the org can't see the light you chose, point your moth-nature at a fire that is deep and counts. This isn't selling out; it's refusing to be consumed anonymously.
Believe what the org is telling you, and go. If you've made the work fully legible, asked plainly, and still nothing — that is not a mystery to keep solving, it's an answer. The org has shown you what it values, and Reputation Forms Early and Updates Slowly means the "good executor" label is often only resettable in a new context. This is Achilles' most rational unused option: leave, and be the named owner somewhere that will hand you the bonfire. The moth that isn't fed carries its flame to a better fire.

And underneath all three, the one asset the disappointment cannot touch: the work made you good, and being good is portable. A promotion is one company's opinion, withheld or granted on that company's politics. The skill is yours in every building you ever walk into. That is not a consolation prize — it is the reason the craving must never be allowed to hollow out the work, because the work is the one thing that survives the org that failed to see it. Be the moth because it earns respect; keep being the moth especially when it doesn't, because the fire is the only part no committee gets to vote on.

What to actually do

Fly into the flame first. Before any of the rest, do work worth remembering — go all the way into the hard problem, the one everyone else surveyed and left. Everything below is a multiplier, and a multiplier on nothing is nothing. Be the moth before you manage the record of being the moth.
Make the work carry your name — at whatever scale you operate. Be the listed author of the doc, not the "thanks to" at the bottom. Be the person who wrote the migration plan the team keeps citing, the runbook everyone reaches for, the doc every new hire is handed. You don't need a famous invention; you need work the org can't narrate without saying your name. These resist compression because they are the record. This is the constructive form of Scope Is Taken, Not Granted: the recurring pain nobody's charter covers is exactly where you can plant a name that can't be reassigned.
Narrate your own work before someone narrates it for you — this is the deliberate trip back for the certificate. Send the wrap-up the week it ships, in a public channel, with a number in it: "Cut onboarding from 3 days to 4 hours; here's the doc." Whoever tells the story owns it, so be first. What feels obvious to you is genuine news to them (Obvious to you. Amazing to others.). This isn't bragging: bragging is about you, narration is about what your work now lets other people do. Do it on the pieces that matter; you don't report every lamp, you report the fire you entered.
Refuse the buyout; name the real currency. If your name isn't on the work, a raise doesn't fix it — that's Agamemnon's gift package, engineered to make a recognition problem look settled. Say the true thing plainly: "I'm glad about the comp. Separately, I want the ownership of this reflected where it counts." Keep the two currencies distinct in your own head, because the org is counting on you to blur them.
Correct taken credit in the room — lightly, and with a date attached. "Glad the approach landed — that's the plan from my doc in March; here's what we've added since." Factual, warm, anchored to a dated artifact, pointed forward. A citation, not an accusation. Dated docs and sent messages turn a correction into evidence instead of a complaint. (This is the boundary in Give Credit Away: being generous with credit is not the same as letting yours be taken.)
Give credit away lavishly yourself — it signals surplus, not scarcity. The counterintuitive economics: naming others raises your standing, because only people with plenty give it away. Hoarding reads as junior no matter your level. Be the person others angle to work with. See Give Credit Away and Easy to Work With Beats Brilliant.
Don't route your whole story through the one person who profits from claiming it. Build Skip-Level Relationships and real peer relationships so more than one mouth tells your story upward. A sponsor who names you in rooms you're not in beats a mentor who praises you to your face (Mentor vs Sponsor). If your only witness is the person who benefits from owning your work, you've handed them the pen.
Use the in-absentia test on your own leads — and become the lead who passes it. Does yours credit you when you're not in the room? When it's your turn, be the one who does. The credit-giver is the anti-Agamemnon, and organizations keep a long, accurate memory of both kinds.

Diagnostic test

Your best win from the last six months — is there a dated, forwardable artifact with your name on it, or does it live only inside someone else's "drove X across the team"?
When your systems break at 3am, does the page come to you? If yes, does the credit for those systems also land on you at review — or on someone in a room you weren't in?
Could your skip-level name one specific thing you did, with a number, without your manager translating it first?
In your last launch note or postmortem, whose names appeared — and was yours attached to the work you actually did, in words you'd be glad to see forwarded up two levels?
Honest one: in the last quarter, did you fly into a flame — go all the way into a genuinely hard problem — or did you spend it surveying lamps and filing reports? A perfect record on questions 1–4 with a "no" here means you've learned to look like a moth. That's just a well-dressed fly.

Two or more uncomfortable answers on 1–4 means the record of your work has drifted toward the king, and the record is what gets remembered. The fix isn't resentment, and it isn't sitting in your tent. It's this: be consumed by the light like the moth — do the work that's worth flying into — and come back just often enough to be remembered on purpose, so the standing you earn carries you to a bigger flame. Agamemnon was right about the quarter and wrong about the decade. The fly kept its life and stayed a fly. Be the moth.