Identity Before Behaviour: What Developers Can Teach Us About the AI Shift

The moment it landed

"Our developers have lost their passion for coding."

That's what someone said at a recent workshop on AI readiness. "Claude can do it as well as we can now."

I heard it. I held it. And then I said what I always say.

This isn't a skills problem. This is an identity problem.

These developers didn't just learn to code. They became coders. It's who they are. It's how they see themselves. It's what got them up in the morning.

And now something else can do it. Faster. Cheaper. Without sleeping.

Of course they've lost their passion. They're grieving.

But here's what I also know

Developers are the ones who understand systems, logic, architecture, and what breaks. Small businesses are crying out for people who can walk in, look at their processes, and say "here's where AI fits, and here's where it doesn't."

That's not a developer. That's an AI Architect. That's a Data Analyst. That's the person who translates the technology for the humans.

Three things I'd say to any developer sitting with that feeling now

1. Let yourself grieve it. Properly. You built something real. That matters.

2. Look at what you actually know. You don't just know code. You know how systems think and work. That skill is rarer than you realise, and small businesses need it desperately.

3. Get ahead of everyone else. You understand AI better than most people in any room. Stop competing with it. Start leading others through it.

The thin end of the wedge

The developers aren't first because they're most at risk. They're first because they're most ready.

Every industry is coming. The question is whether you grieve your old identity or start now to build the next one.

Identity before behaviour. Always.