The Builder Identity Shift for Software Engineers

The identity trap

Peter Steinberger, creator of OpenClaw, spent a year giving talks at iOS developer conferences in 2025 and early 2026. The message he kept delivering was consistently unwelcome:

“Don't see yourself as an iOS developer anymore. You need to change your mindset. You're a builder.”

He told Lex Fridman that people didn't like hearing it. That's understandable. When you've spent years mastering a craft, when your identity is bound up in being excellent at a specific thing, being told that specific thing is becoming less economically central feels like a threat.

But Steinberger wasn't saying iOS development was worthless. He was saying the identity was too small. The skills are valuable — the narrow self-conception is the problem.

Programming is becoming like knitting

Here is the honest account of where hand-written code is headed, as articulated by one of the most thoughtful practitioners working at the frontier of AI-assisted development:

“The actual art of programming — it will stay there, but it's going to be like knitting. People do that because they like it, not because it makes any sense. The craft of hand-writing code will become something people pursue because they love it. And there's something meaningful in that. But it won't be the primary economic activity it once was.”

Steinberger added: “I can relate that if you very deeply identify that you are a programmer, that it's scary and threatening because what you like and what you're really good at is now being done by a soulless — or not — entity. But I don't think you're just a programmer. That's a very limiting view of your craft. You are still a builder.”

The people who handle this transition worst are those who have the most tightly coupled identity — the ones who think “I am a programmer” rather than “I am someone who builds things, and programming is one of the tools I use to do that.”

What the job market shift actually looks like

Steinberger was direct about the economic reality: “There was a lack of intelligence — people who could build things — and that's why salaries of software developers reached stupidly high amounts. And then they will go away.”

But he was equally clear about what follows: “There will still be a lot of demand for people that understand how to build things. It's just that all this tokenized intelligence enables people to do a lot more, a lot faster.”

This is an important distinction. The demand for people who can type code from memory into an editor is declining. The demand for people who understand how to build things — who can make product decisions, architect systems, communicate clearly, and direct AI agents toward coherent goals — is growing.

The skills that matter most in this transition:

• System thinking. Understanding how components interact, where complexity lives, and how architecture decisions compound over time. This is why experienced engineers who “can't vibe code” still have so much value — they've internalized patterns that agents can't easily replicate.
• Product sense. What should be built? How should it feel? What's the right scope? Agents can implement almost anything. The hard part is knowing what to implement.
• Communication precision. The ability to express ideas clearly — to humans and to agents — is now a core engineering skill. Ambiguous prompts produce ambiguous software. Clear thinking produces clear output.
• Judgment under uncertainty. When the agent's solution is good enough vs. when it needs human intervention. When to ship vs. when to refactor. When to follow the agent's lead vs. when to push back. This is taste, built from experience.

Non-programmers are already building 25 web services

Steinberger runs a meetup he calls “Agents Anonymous.” At one session, a design agency owner approached him with a story that captures the current moment:

“I run this design agency, and we never had custom software. And now I have 25 little web services for various things that help me in my business. And I don't even know how they work, but they work. He was just very happy that this stuff solved some of his problems. And he was curious enough that he actually came to an agentic meetup, even though he doesn't really know how software works.”

Twenty-five custom web services. No programming background. This isn't a fluke — it's a preview.

For professional developers, this is both a challenge and an opportunity. The challenge: the bar for “being able to build software” has dropped so dramatically that the credential itself is worth less. The opportunity: the bar for building software that is actually excellent, robust, maintainable, and well-architected has never been higher — because there's now so much software being built by people who don't know how to do those things.

What “builder” actually means in practice

When Steinberger talks about the builder identity, he's describing something specific — not just a philosophical reframe. Builders in the agentic engineering era share several concrete characteristics:

• They work across tech domains. Steinberger described moving fluidly between Swift, Go, TypeScript, and Zig — picking the language that fits the problem, not the one they're most comfortable with. “You can take a lot of knowledge about how to build software into new domains. The fine-grain details, agents can help. You don't have to know the correct template syntax or how to splice an array. You can use your general knowledge — that makes it much easier to move from one tech galaxy to another.”
• They care about delight, not just functionality. Steinberger added small messages to OpenClaw that appear when it updates: “Built on Caffeine, JSON5, and a lot of willpower.” Little things that make users smile. “An agent would not come up with that by itself. That's just how you build software that delights.” Human taste, creativity, and care remain differentiators that AI can't fully replicate.
• They say no as much as yes. “Thinking hard about what should be in core, what's an experiment, where to say no — even if people send a PR and I like that feature. Maybe this should not be part of the project. Maybe we can make it a skill or plugin. There is still a lot of craft and thinking involved in how to make something.”
• They understand the user's world. The design agency owner who built 25 web services did so because agents helped him. His understanding of what his agency needed — his domain knowledge about running a design business — is what made those services useful. Technical capability without domain knowledge builds things nobody wants.

The mourning that comes with this transition

There's something worth acknowledging directly. Steinberger said it clearly, and Lex Fridman echoed it: the transition to AI-assisted development involves genuine loss for developers who built their identity around the craft of programming.

“I read this article about someone who wrote that it's okay to mourn our craft. And I strongly resonate with that. In my past I spent a lot of time tinkering, just being really deep in the flow, cranking out code, finding really beautiful solutions. In a way, it's sad because that will go away. I also get a lot of joy out of just writing code and being really deep in my thoughts and forgetting time and space. But you can get the same state of flow by working with agents and building and thinking really hard about problems. It is different — but it's okay to mourn it.”

This isn't a call to deny the difficulty of the transition. It's a call to not get stuck in the mourning. Because at the other end of the transition is a different kind of flow — one that comes from directing systems toward meaningful outcomes rather than from implementing them line by line.

What “coding” will mean in five years

Steinberger made a prediction that's worth sitting with: “I think at some point it's just gonna be called coding again, and it's just gonna be the new normal. And yet, while I don't write the code, I very much feel like I'm in the driver's seat and I am writing the code. It's just a different activity.”

The word stays. The activity changes. And the activity of directing AI agents toward complex engineering goals is still fundamentally creative, still requires expertise and judgment, and still produces real things of real value. It's just that the bottleneck has shifted — from “how do I implement this” to “what should I build and how should it work.”

That shift actually puts experienced, thoughtful developers in a better position than they might realize. The engineers who understood system design, product thinking, and software architecture before AI tools arrived have the hardest-to-replicate skills of this era. What they need to add is the practical fluency with AI agents — and the willingness to expand their identity from “programmer” to “builder.”

Practical steps for the identity shift

If you're a developer who wants to make this transition successfully, here are concrete actions that matter more than any specific technology choice:

1. Stop specializing in frameworks, start building things. The framework expertise that made you valuable in 2020 is much easier for an AI to generate in 2026. What can't be replicated is your understanding of what to build and why.
2. Work on your product sense. Use the products you build. Talk to users. Develop opinions about what's good and what isn't. This is the judgment that survives the AI transition.
3. Get fluent with agents, not just AI tools. There's a difference between using Copilot for autocomplete and running an agentic workflow. Get comfortable with the latter.
4. Move across domains. The most valuable builders in the next era will be the ones who can bring software capabilities to domains they understand deeply — healthcare, education, logistics, finance. Domain knowledge + builder skills is a powerful combination.
5. Find companies that already think this way. The best remote developer jobs right now are at companies that understand the distinction between “programmer” and “builder” — and hire accordingly. These are the environments where the identity shift is already happening.

The developers who will thrive in the next five years aren't necessarily the ones who write the most beautiful code. They're the ones who think biggest — who understand what they're capable of building, and who expand their identity to match.

You're not an iOS developer. You're not a backend engineer. You're not a Python specialist. You're a builder. And the tools available to builders right now are the most powerful in human history.

Keep reading

• Vibe Coding Career Path
• What Is Vibe Coding
• Career Change To Vibe Coding