---
title: "Ego-Less: Rebuilding Without Breaking"
url: "http://coey.dev/ego-less"
source: "coey.dev"
---

<div class="absolute inset-0 z-1 pointer-events-none h-40vh">![](/images/ego.jpg)
<section class="flex justify-center relative overflow-hidden min-h-50vh min-h-50dvh items-center bg-black overflow-hidden svelte-1ylxfcw"> <div class="relative z-10 text-center p-8 pt-40 flex flex-col items-center svelte-1ylxfcw"> <h1 class="text-[clamp(3.5rem,14vw,9rem)] font-black tracking-[0.08em] leading-[0.9] text-white m-0 bh-title-transition opacity-0 translate-y-3 blur-[4px]  svelte-1ylxfcw">EGO-LESS
<p class="font-mono text-[clamp(0.7rem,1.8vw,0.95rem)] tracking-[0.2em] uppercase text-[#555] mt-8 bh-subtitle-transition opacity-0 translate-y-2.5  svelte-1ylxfcw">Rebuilding Without Breaking
<div class="mt-12 bh-scroll-transition opacity-0 translate-y-2.5 svelte-1ylxfcw"><span class="block w-px h-12 mx-auto bh-pulse svelte-1ylxfcw" style="background: linear-gradient(to bottom, transparent, #333)"></span>

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><p class="el-opening svelte-swp5je">Why does it sting when someone rewrites your code?
It's just code. Right?

<section class="el-section el-section-tight svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">I design things. I put them in front of people. Sometimes they say "this doesn't work."
And for a half-second, my brain hears "you don't work."

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">I write code. I ship it. Someone refactors the whole thing. And for a half-second,
I feel erased.

<div class="el-stagger el-callout svelte-swp5je"><p class="svelte-swp5je">That half-second is the ego. The rest is craft.

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#a1a1aa"></span> <span>The Original Idea</span>
<div class="el-body svelte-swp5je"><div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">In 1971, Gerald Weinberg published _The Psychology of Computer Programming_.
He coined a term: **egoless programming**. The idea was simple.
Code should be reviewed by others. I've learned to welcome that review.
Your code is not your identity.

<div class="el-stagger el-ref-card svelte-swp5je"><span class="el-ref-tag svelte-swp5je">Book</span> <span class="el-ref-title svelte-swp5je">The Psychology of Computer Programming</span> <span class="el-ref-meta svelte-swp5je">Gerald Weinberg, 1971</span> <p class="el-ref-note svelte-swp5je">"The whole point of egoless programming is not that you have no ego,
but that you don't let it interfere with what you're trying to accomplish."

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Weinberg wasn't saying don't care. He was saying separate the caring
from the defending. Care about the outcome. Don't defend the path
you took to get there.

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">The design world got there through a different door.
"Kill your darlings" .. Arthur Quiller-Couch (1914), popularized by Faulkner, practiced by every
designer who ever shipped something. IDEO built an entire methodology
around it: prototype fast, test with real people, throw away what
doesn't work. The prototype is disposable. The insight it generates isn't.

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#78716c"></span> <span>Two Doors, Same Room</span>
<div class="el-body svelte-swp5je"><div class="el-stagger el-two-col svelte-swp5je"><div class="el-col el-col-design svelte-swp5je"><h4 class="el-col-title svelte-swp5je">Design
<ul class="svelte-swp5je"><li class="svelte-swp5je">You present a mockup
<li class="svelte-swp5je">Someone says "the hierarchy is wrong"
<li class="svelte-swp5je">Your instinct: they're calling you a bad designer
<li class="el-col-correct svelte-swp5je">What they meant: the layout doesn't communicate priority

<div class="el-col el-col-dev svelte-swp5je"><h4 class="el-col-title svelte-swp5je">Development
<ul class="svelte-swp5je"><li class="svelte-swp5je">You ship a feature
<li class="svelte-swp5je">Someone rewrites your implementation
<li class="svelte-swp5je">Your instinct: they're saying your code was bad
<li class="el-col-correct svelte-swp5je">What they meant: requirements changed, or they found a simpler path

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Both moments require the same skill: receiving the feedback without
letting it puncture your willingness to try again. Having enough pride
to put something forward you're willing to stand by. Having enough
absence of ego to let someone else improve it.

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#3b82f6"></span> <span>What the Research Says</span>
<div class="el-body svelte-swp5je"><div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Carol Dweck's work on mindset puts it in sharp relief.
A **fixed mindset** treats ability as identity .. criticism of output
becomes criticism of self. A **growth mindset** treats ability as
something that develops .. criticism of output becomes data for iteration.

<div class="el-stagger el-ref-card svelte-swp5je"><span class="el-ref-tag svelte-swp5je">Research</span> <span class="el-ref-title svelte-swp5je">Mindset: The New Psychology of Success</span> <span class="el-ref-meta svelte-swp5je">Carol Dweck, 2006</span> <p class="el-ref-note svelte-swp5je">Fixed mindset: "If I have to work hard, it means I'm not talented."
Growth mindset: "If I have to work hard, it means I'm growing."

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Amy Edmondson at Harvard built on this with **psychological safety** ..
the idea that teams perform better when members feel safe to take interpersonal
risks. In her study of hospital teams, the best-performing units reported _more_ errors, not fewer. They weren't making more mistakes. They felt
safe enough to surface them.

<div class="el-stagger el-ref-card svelte-swp5je"><span class="el-ref-tag svelte-swp5je">Research</span> <span class="el-ref-title svelte-swp5je">The Fearless Organization</span> <span class="el-ref-meta svelte-swp5je">Amy Edmondson, 2018</span> <p class="el-ref-note svelte-swp5je">Google's Project Aristotle confirmed it: psychological safety was the single
best predictor of team effectiveness. Not talent. Not process. Safety.

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">It's consistent: when my identity isn't at stake, I can see
what's actually happening. When it is, every signal gets filtered
through "what does this say about me?"

<section class="el-section el-section-demo svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#f59e0b"></span> <span>The Spectrum</span>
<div class="el-spectrum-wrap svelte-swp5je"><div class="el-spectrum-labels svelte-swp5je"><span class="el-spectrum-end svelte-swp5je">Detached</span> <span class="el-spectrum-end svelte-swp5je">Attached</span>
<input type="range" class="el-slider svelte-swp5je" min="0" max="100" value="50"/> <div class="el-spectrum-readout svelte-swp5je" style="color: #a8a29e">You care. Criticism stings but doesn't stop you.
<div class="el-spectrum-callout svelte-swp5je"><p class="svelte-swp5je">The sweet spot isn't zero ego. It's **enough ego to care, not enough to break**.
Caring deeply about the work without fusing your identity to any single expression of it.

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#ef4444"></span> <span>The Case for Caring</span>
<div class="el-body svelte-swp5je"><div class="el-stagger el-callout el-callout-red svelte-swp5je"><p class="svelte-swp5je">But ego-less can also be lazy.

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Ed Catmull, co-founder of Pixar, describes the creative process as inherently
painful. The early versions of every Pixar film were, in his words, "ugly babies."
The team had to care enough to keep working through the discomfort, not
detach from it. Pure detachment produces commodity work. The films that move
people come from people who were willing to be moved themselves.

<div class="el-stagger el-ref-card svelte-swp5je"><span class="el-ref-tag svelte-swp5je">Book</span> <span class="el-ref-title svelte-swp5je">Creativity, Inc.</span> <span class="el-ref-meta svelte-swp5je">Ed Catmull, 2014</span> <p class="el-ref-note svelte-swp5je">"If you aren't experiencing failure, then you are making a far worse mistake:
you are being driven by the desire to avoid it."

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Paul Saffo's framework: "strong opinions, weakly held." Argue your position
with conviction, then drop it the moment better evidence arrives. Jeff Bezos
had his own version: "disagree and commit." Different phrases, same move.
The conviction isn't the problem. The inability to release it is.

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Dieter Rams spent decades refining ten principles of good design.
Principle ten: "Good design is as little design as possible."
That requires ego .. the confidence to subtract. And then the
absence of ego .. the willingness to subtract your own favorite parts.

<div class="el-stagger el-quote-switcher svelte-swp5je"><button class="el-quote-tab svelte-swp5je el-quote-tab-active">Design</button><button class="el-quote-tab svelte-swp5je">Development</button><button class="el-quote-tab svelte-swp5je">Craft</button> <div class="el-quote-body svelte-swp5je"><p class="el-quote-text svelte-swp5je">Your first draft is a conversation opener, not a thesis defense.
<p class="el-quote-desc svelte-swp5je">The prototype isn't precious. The problem it solves is.

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#22c55e"></span> <span>The AI Mirror</span>
<div class="el-body svelte-swp5je"><div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">AI is forcing this conversation in a new way.
<p class="mt-4 svelte-swp5je">You write a function. An LLM rewrites it in 3 seconds. Different approach,
same outcome, fewer lines. Your instinct: that should have been my solution.
But the function works. Does it matter whose pattern it followed?

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">Egoless programming asked whether I could accept a colleague's review
without defending the code as part of myself. Agent-written code adds a
similar test: can I judge the patch without treating who wrote it as a
judgment about my value?

<div class="el-stagger el-callout svelte-swp5je"><p class="svelte-swp5je">The developers who thrive in this environment aren't the ones who write
the most code. They're the ones who can look at output .. theirs or the
machine's .. and honestly evaluate whether it solves the problem.

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">In Dell'Acqua et al.'s consulting experiment, participants using AI
completed more tasks faster and with higher measured quality on tasks
inside the model's capability frontier. Performance dropped outside that
frontier, which made evaluation more important than raw tool use.

<div class="el-stagger el-ref-card svelte-swp5je"><span class="el-ref-tag svelte-swp5je">Research</span> <span class="el-ref-title svelte-swp5je">Navigating the Jagged Technological Frontier</span> <span class="el-ref-meta svelte-swp5je">Dell'Acqua et al. (incl. Mollick), Harvard/Wharton, 2023</span> <p class="el-ref-note svelte-swp5je">Consultants using AI completed 12.2% more tasks, 25.1% faster,
with 40% higher quality. But only when they maintained critical judgment.

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#a78bfa"></span> <span>The Deeper Layer</span>
<div class="el-body svelte-swp5je"><div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">The design critique, the code review, and the AI rewrite all expose
the same question: _can you let something you made be changed
without feeling like you've been changed?_

<div class="el-stagger el-philosophy-grid svelte-swp5je"><div class="el-phil svelte-swp5je"><span class="el-phil-tradition svelte-swp5je">Stoicism</span> <p class="el-phil-teaching svelte-swp5je">Stoic writing separates choices from outcomes. That distinction helps me hear a critique without pretending I can control the response.

<div class="el-phil svelte-swp5je"><span class="el-phil-tradition svelte-swp5je">Buddhism</span> <p class="el-phil-teaching svelte-swp5je">Buddhist writing on non-attachment gives me language for caring about work without treating it as a stable identity.

<div class="el-phil svelte-swp5je"><span class="el-phil-tradition svelte-swp5je">Wabi-sabi</span> <p class="el-phil-teaching svelte-swp5je">Wabi-sabi values imperfection and impermanence. I use that as a reminder that a changed design is not automatically a damaged one.

<div class="el-phil svelte-swp5je"><span class="el-phil-tradition svelte-swp5je">Ship of Theseus</span> <p class="el-phil-teaching svelte-swp5je">The Ship of Theseus asks what remains when each part is replaced. A software project raises a smaller version of that question after enough rewrites.

<div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">These traditions are not software methods. They are references I use when a rewrite
feels more personal than it is. The practical step is simpler: separate the quality
of the change from the feeling of being changed.

<section class="el-section svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-era-label svelte-swp5je"><span class="el-era-marker svelte-swp5je" style="background:#e5e5e5"></span> <span>The Practice</span>
<div class="el-body svelte-swp5je"><div class="el-stagger el-narrative svelte-swp5je"><p class="svelte-swp5je">So. How do you care enough to make good work but not so much that criticism breaks you?

<div class="el-stagger el-practice-list svelte-swp5je"><div class="el-practice svelte-swp5je"><span class="el-practice-num svelte-swp5je">1</span> <div><p class="el-practice-title svelte-swp5je">Separate the work from the worker.
<p class="el-practice-desc svelte-swp5je">"The design has a hierarchy problem" is not "you are a bad designer." Train yourself to hear the noun, not feel the verb.

<div class="el-practice svelte-swp5je"><span class="el-practice-num svelte-swp5je">2</span> <div><p class="el-practice-title svelte-swp5je">Ship early, before you're proud.
<p class="el-practice-desc svelte-swp5je">If you wait until you love it, you've already fused with it. Share while it's still rough. The feedback hurts less when you know it's a draft.

<div class="el-practice svelte-swp5je"><span class="el-practice-num svelte-swp5je">3</span> <div><p class="el-practice-title svelte-swp5je">Measure by outcomes, not authorship.
<p class="el-practice-desc svelte-swp5je">Did the user find the button? Did the test pass? Did the feature ship? Who wrote the code doesn't matter. What the code does matters.

<div class="el-practice svelte-swp5je"><span class="el-practice-num svelte-swp5je">4</span> <div><p class="el-practice-title svelte-swp5je">Practice being wrong publicly.
<p class="el-practice-desc svelte-swp5je">The more you survive being wrong, the less being wrong threatens you. Normalize it. Make it boring. The ego can't grip something that happens every Tuesday.

<div class="el-practice svelte-swp5je"><span class="el-practice-num svelte-swp5je">5</span> <div><p class="el-practice-title svelte-swp5je">Rewrite your own work before someone else does.
<p class="el-practice-desc svelte-swp5je">Go back to code you wrote six months ago. Refactor it. You'll realize: the person who wrote it was doing their best with what they knew. And you can still make it better. That's not failure. That's growth.

<section class="el-section el-section-last svelte-swp5je"><div class="el-container svelte-swp5je"><div class="el-closing svelte-swp5je"><p class="el-closing-text svelte-swp5je">I'm still figuring this out.
I want to care about what I make
without needing it to stay the way I made it.
<p class="el-closing-kicker svelte-swp5je">The work is not me.
The willingness to keep making it is.

<div class="el-references svelte-swp5je"><h3 class="el-ref-section-title svelte-swp5je">References
<div class="el-ref-list svelte-swp5je"><p class="svelte-swp5je">Weinberg, Gerald. _The Psychology of Computer Programming_. Van Nostrand Reinhold, 1971. [Dorset House (publisher)](https://www.dorsethouse.com/books/psy.html)
<p class="svelte-swp5je">Dweck, Carol. _Mindset: The New Psychology of Success_. Random House, 2006. [Penguin Random House](https://www.penguinrandomhouse.com/books/44330/mindset-by-carol-s-dweck/)
<p class="svelte-swp5je">Edmondson, Amy. _The Fearless Organization_. Wiley, 2018. [Wiley](https://www.wiley.com/en-us/The+Fearless+Organization%3A+Creating+Psychological+Safety+in+the+Workplace+for+Learning%2C+Innovation%2C+and+Growth-p-9781119477266). See also: Google's [Project Aristotle](https://rework.withgoogle.com/intl/en/guides/understanding-team-effectiveness).
<p class="svelte-swp5je">Catmull, Ed. _Creativity, Inc._ Random House, 2014. [Random House](https://www.randomhousebooks.com/books/216369/)
<p class="svelte-swp5je">Dell'Acqua et al. "Navigating the Jagged Technological Frontier." Harvard Business School, 2023. [Pdf](https://www.hbs.edu/ris/Publication%20Files/24-013_d9b45b68-9e74-42d6-a1c6-c72fb70c7571.pdf)
<p class="svelte-swp5je">Saffo, Paul. "Strong Opinions, Weakly Held." Coined the framework; popularized 2008. [EDUCAUSE interview (1998)](https://library.educause.edu/resources/1998/1/paul-saffo-interview-betting-on-strong-opinions-weakly-held), [rc3.org (2008)](https://rc3.org/2008/08/25/strong-opinions-weakly-held/).
<p class="svelte-swp5je">Rams, Dieter. "Ten Principles for Good Design." [Vitsoe](https://www.vitsoe.com/us/about/good-design).
<p class="svelte-swp5je">Mollick, Ethan. _Co-Intelligence: Living and Working with AI_. Portfolio, 2024. [Penguin Random House](https://www.penguinrandomhouse.com/books/741805/co-intelligence-by-ethan-mollick/)

<div class="el-related svelte-swp5je"><h3 class="el-related-title svelte-swp5je">Related
<ul class="el-related-list svelte-swp5je"><li class="svelte-swp5je">[Patience](/patience) <span>.. Leaving better notes. The patience companion piece.</span>
<li class="svelte-swp5je">[Campfire](/campfire) <span>.. Stories, prompts, and context limits.</span>
<li class="svelte-swp5je">[Puzzle](/puzzle) <span>.. The algorithm you already know. You are the heuristic, not the solution.</span>

<div class="mx-auto max-w-6xl px-6 md:px-12 hidden"><section class="border-t border-black/10 py-16 md:py-24"><div class="max-w-4xl"><div class="text-3xl md:text-5xl font-black tracking-tight leading-[1.05]">Get new posts by email.
<div class="mt-4 font-mono text-black/70 text-lg md:text-xl">Join 5 other subscribers.
<div class="mt-8"><button class="border-4 border-black bg-black text-white px-8 py-4 text-xl font-black hover:bg-white hover:text-black">Subscribe</button>
