Skip to main content
Articles / When Coding Became My Identity

Article

When Coding Became My Identity

Alek reflects on twenty years of coding, the pressure to keep up with AI, and learning to separate his skills from his identity.

← Back to articles

In one line

Chasing tools to stay ahead led Alek to burnout.

Read time

2 min

Focus

AI

Work

When AI first started coming out, I started freaking out. I had been coding for twenty years. Being a developer was tied up with who I was, and suddenly I wasn’t doing the same work.

I felt the demand for the kind of work I knew was changing. My response was to try to get ahead of the curve: learn more tools, build my own systems for working with AI, keep going.

That led to burnout.

What people needed from me

I was putting all this effort into what I could build behind the scenes. But I came to realize that the people looking for my help weren’t interested in that part. They wanted to know whether I could fix their problem.

That gave me something different to focus on. I could spend my energy trying to keep up with every change in how software gets built, or I could focus on the problem someone needed me to solve.

The second approach meant changing how I thought about my own work. Coding had been a skill I’d practised for twenty years. I had also made it part of my identity, which made changes to the work feel personal.

Separating those things wasn’t easy. I had to stop treating the amount of coding I was doing as the measure of who I was.

If you’re feeling that same pressure to learn more tools just to stay ahead, start with the question I had to come back to: what problem does someone need you to fix?

Next step

Need help finding the first problem worth fixing?

Pre-Flight helps you choose one useful place to begin.

Newsletter

Get practical ops insights once a week

No spam. Unsubscribe anytime.

Read next

Canadian Owned. Canadian Operated.