I saw a line in a LinkedIn thread recently that named this better than most research papers have: “The real fear isn’t replacement; it’s decoupling, losing the thread between what we build and why it works”. That’s the third fault line, and I think it’s the deepest one, because it doesn’t show up as a missing title or a devalued skill. It shows up as a quiet, hard-to-explain feeling that you’re no longer the one building anything. You’re the one watching something else build and initialing the result.
I’ve felt this one myself. Somewhere in the last year, my own work shifted from writing code to reviewing what an agent wrote, from drafting the plan to approving someone else’s plan, except the “someone else” is software. One developer described the same arc publicly: “This feels like moving from execution to decision-making, which is a significant change in mindset”. Notice the word he didn’t reach for — he didn’t say “worse.” He said “different.” That distinction matters, and it’s the one I want to spend this whole post on.
Why “Am I Still Building?” Is a Different Question Than Title or Skill
Decades of research on meaningful work converge on three separable ingredients: significance (does this matter), self-realization (am I expressing something of myself through this work), and broader purpose (does it serve something beyond me). Title loss threatens significance — the “does this matter, and does anyone see that it matters” part. Skill obsolescence threatens self-realization — the “am I expressing my own capability” part. But this third fault line goes after something underneath both: the felt experience of authorship. It’s possible to still have a title, still have a marketable skill, and still feel hollowed out. Because the thing that used to be yours, the artifact, the thing you pointed at and said “I made that”, now has someone else’s fingerprints on it, or no fingerprints at all.
There’s a well-documented psychological reason handmade things feel more valuable to us than mass-produced ones: researchers call it the “effort heuristic.” We judge value partly by the visible human effort baked into a thing. That heuristic doesn’t just apply to how we value objects. It applies to how we value ourselves. If the effort is increasingly the AI’s and the judgment call is increasingly yours, some part of you is going to keep asking whether “I built this” is still an honest sentence.
The Uncomfortable Middle Ground: You’re Not Wrong to Feel This
I want to resist the easy move here, which is to just reassure you that orchestration is “just as real” as building. Sometimes it is. Sometimes it genuinely isn’t, and pretending otherwise is condescending. Design and craft researchers make a sharp version of this argument: AI can generate the “what” in seconds, but it can’t answer the “why”. It can’t sense the unspoken tension in a room or know when to break a convention deliberately, because that requires the messy, slow, human work of actually sitting with a problem. Craftsmanship isn’t sentimental. It’s a specific kind of knowledge; researchers studying makers describe “embodied intelligence,” the knowledge that lives in your hands and your mileage, not just your head, and that kind of knowing genuinely doesn’t transfer to a screen.
So here’s the honest tension I think this post needs to sit in, without resolving it too fast: some of what’s being lost really is a loss. Not every form of “orchestrating instead of doing” is a promotion in disguise. And at the same time, not every act of building requires your hands on the keyboard. Plenty of what made your old work meaningful was never really the typing. It was the decision about what to type and why and for whom.
The Research on What Actually Restores the Feeling of Contribution
If the injury is decoupling — losing the thread between the work and the reason it matters — the research on meaningful work points to a specific repair: autonomy and a felt sense of prosocial impact are the two factors longitudinal studies find most reliably predict people experiencing their work as meaningful over time. Neither of those requires you to personally type every line. Autonomy is about having real say in what gets built and how. Prosocial impact, “beneficence,” in the research language, is about seeing, concretely, that your decisions changed something for someone. Both of those are still fully available to a person orchestrating AI output, arguably more available, since AI can free up the time that used to go into execution and hand it back to the parts of the job. Talking to users, making calls, and setting direction actually generate that sense of contribution.
This is, I think, the real substance behind the “conductor, not doer” reframe I’ve written about before: the shift from being paid for artifacts to being paid for judgment. It’s not a slogan meant to paper over a real loss. It’s a specific claim about where meaning was always actually located: not in the typing but in the decision that the typing served.
A Warning From the Research: Don’t Let the Machine Write Your Inner Narrative
There’s a subtler risk worth naming here, one I think is underappreciated in most AI-and-work commentary. Some researchers describe a phenomenon they call “identity drift” — a gradual process where a person’s sense of self starts aligning with the feedback loop of the system they work inside, rather than with their own internal sense of what’s true or good. Applied here: if your only signal of whether your work matters becomes “did the AI’s output get accepted,” you can slowly stop asking whether it was actually the right output and start asking only whether it was an approved one. That’s not a hypothetical. It’s the quiet failure mode of orchestration done without reflection. You keep your job, but you lose the thread the LinkedIn commenter was talking about.
The corrective the research points to is almost embarrassingly simple: pause before you approve and ask, “Is this mine?” not in a legal authorship sense, but in the sense of whether you actually stand behind the judgment behind it. That single habit is the difference between orchestration as a genuine evolution of contribution and orchestration as a slow outsourcing of your own judgment to whatever the system produces.
What to Actually Do With This Monday Morning
- Ask your team, directly: “What does ‘I built something’ mean to you now?” Don’t supply the answer. Let the discomfort in the answer tell you where someone actually is.
- Don’t rush past real grief with a reframe. If someone genuinely misses the craft of typing the thing themselves, that’s not a mindset problem to be coached away; some of it is a real loss, and it deserves to be named as one.
- Redirect freed-up time toward the two things the research says actually rebuild meaning: give people more real say in decisions (autonomy) and a more direct line of sight to who benefits from those decisions (impact).
- Build in the “Is this mine?” pause before sign-off as a team habit, not just a personal one. It’s the cheapest defense against quietly outsourcing judgment to the tool.
Where I Land, For Now
Across all three posts in this series, I keep landing in the same place: the title, the skill, and the sense of building were never actually the point. They were proxies — visible, countable stand-ins for something harder to see, which is judgment, exercised on behalf of someone else, that you’re willing to stand behind. AI is taking the proxies, one at a time. It hasn’t yet figured out how to take the willingness to stand behind a decision. That’s still yours. The work now is making sure you notice it’s still yours, instead of quietly handing it away because the artifact doesn’t look like it used to.
- My company is forcing me to become AI-agent dependent – Managers think Cursor is magic.” They understand non-complicated metrics like lines of code created …
- AI Agents Are Replacing Developers? My Honest … – They operate across the entire codebase, which makes them feel less like tools and more like junior …
- How I Went From Writing Code to Managing AI Agents Full-Time – Most developers think the IDE versus TUI debate is about tools. It’s actually about management style…
- Significant Work Is About Self-Realization and Broader … – by F Martela · 2018 · Cited by 774 — Bailey et al. ( 2017 ) define meaningful work as “work that is …
- The Appeal of Handmade in an Era of Automation – The psychology behind our attraction to the handmade, the bespoke, and the artisanal in an age of in…
- Why Design Craft Still Matters in a World of Automation – True design, the kind that moves people, builds trust, and tells complex human stories, takes more t…
- The Psychology of Craft: What Happens When You Actually … – Designing isn’t the same as making. And your brain knows it. This video dives into what making thing…
- What makes work meaningful? Longitudinal evidence for … – by F Martela · 2021 · Cited by 258 — Beneficence is about the sense of prosocial impact and feeling …
- Happy Pie Day! The Great Inversion Launch – Tim Dickey – Tim Dickey helps software product teams master agile practices, AI fluency, and modern team coaching…
- Authenticity After Automation: Staying Real in an Age … – In psychological terms, identity migrated from the private self to the performed self. Automation di…
Leave a Reply