Coaching engineers through the vibe-coding transition

The senior engineer opposite me has been shipping for twenty-five years. Six minutes ago he ran his first claude code command. I can see his pulse in his neck.

He says the thing they all say, in different words: I don’t know what I am anymore.

He has just watched the agent do in four prompts what he budgeted a day for. The code isn’t quite right — there’s a retry loop he wouldn’t have written. But it works. It ran the tests. It opened the PR. He was the bottleneck for the last nine minutes and he didn’t type a single character.

He is not having a skill crisis. He is having an identity crisis.

What’s actually happening

For most of his career, writing the code has been the evidence of his professional selfhood. The keyboard was where decisions became artifact. The artifact was how he knew he was worth hiring.

When an agent takes over the keystrokes, that circuit opens. The decisions are still his. The taste is still his. The judgment calls about what to even build — those are, if anything, more load-bearing than before. But the thing that proves those qualities to himself is gone.

The panic attack is the psyche noticing that the mirror is cracked.

The wrong moves

When a well-meaning colleague sees a senior engineer in this state, they typically do one of three things, all wrong.

Reassurance: “You’re still valuable.” The worst one. It confirms the thing he’s afraid of — that his value was in question — while offering nothing he can act on. It also comes from the colleague’s own anxiety, not from understanding the senior’s.

Productivity reframing: “You can ship 10x now!” This presumes the problem is about output. It isn’t. He already shipped plenty. The problem is that the medium of his shipping has dissolved.

Tool-shaming: “Old-school developers will always have jobs.” Tempting, generous in intent, functionally cruel. It encourages him to keep his identity welded to a medium that is, in fact, dissolving — and he knows it.

None of these moves meet him where he is.

He is not having a skill crisis. He is having
an identity crisis.

What to say, and when

PCIC-style coaching doesn’t have a script, but it has a shape. With engineers in this transition, three moves cover most of the early work.

“Tell me what you used to feel when you wrote that loop.”

Ask him to describe the physical, pre-verbal satisfaction of writing — the moment of the solution clicking, the way a clean function closed. Make it concrete: a specific loop, a specific refactor, a specific late night.

Most seniors have never been asked this. They assume the feeling is private or embarrassing. Putting language on it does two things at once: it honors what was real, and it separates the feeling from the mechanism that produced it. The feeling was yours. The typing was only one of the ways it got out.

“What about that is still available to you now?”

This is the pivot. Not “will you still get to feel this?” — too abstract, too hopeful. What is available — today, this week, with this agent?

He’ll usually find two or three things. The taste judgment when he reviews the agent’s work. The decision about what to build at all. The architecture call. The “no, we don’t need that dependency.” The way he walks into a messy codebase and sees the through-line nobody else has seen.

These were always there. They were hidden under the typing because the typing took all the attention.

“What do you want to let go of?”

This one is harder. It asks him to name the part of his identity that was downstream of the typing — the craftsman ego, the “I work harder than everyone else because I write more than everyone else,” the identification with being the only one who could hold the whole thing in his head.

Some of that was virtue. Some of it was load-bearing in a way that isn’t serving him anymore. He gets to choose what to carry forward.

Don’t answer the question for him.

What you’re actually coaching for

Not mastery of the tool. Not “AI literacy.” The goal is the integration of the change — a quiet re-seating of identity on what was always underneath the typing.

When this is integrated, the engineer stops trying to prove he’s worth keeping and starts practicing what he’s worth keeping for. The tools become boring again, the way tools are supposed to be.

You can tell it’s landed when he stops asking the agent for instructions and starts giving them. When he cares less about the cleverness of the prompt and more about whether the outcome is what he actually wanted. When he lets the agent write the retry loop he wouldn’t have written, because the retry loop was never the point.

The senior engineers will be fine

Not because they adapt fastest — they often don’t — but because the thing that made them seniors was never the keyboard. It was the 25 years of noticing what happens when you make the wrong decision in hour 40 of a deployment, the pattern recognition, the tolerance for ambiguity, the physical calm when production is on fire. None of that transfers to the agent. All of it becomes more valuable when the typing stops consuming the attention it used to.

The work is learning to recognize that, in yourself, before you watch someone else recognize it in you.

---

Six minutes after the panic attack, the engineer opposite me laughed. Small, dry, real. Then he asked a better question:

“What do I want this thing to do that I haven’t thought to tell it yet?”

That’s the first move of a coach. Also the first move of a senior. He was one all along.