Remember why we do this

I thought I was going to be a medical doctor. Yet, through a series of decisions and complete shifts, I found that I'm captivated by the fact that you can shape electricity in ways that help you find answers to complex questions. To put it simply: create algorithms that surface the truth.

I've been building digital products ever since.

Today, the whole industry is challenging how I build technology and frankly the doom callers will always push for 'your skills are being replaced'. I had to work out if it is the skill of coding itself that we're all so scared of losing. Well if that skill is everything you have, it's quite a ride. Builders, engineers, product people, we're not defined purely by our hard skills. They unlock capability and creativity. But that's not what keeps you in the room.

I think about when I actually feel the rush. It's not shipping fast. It's understanding a problem deeply enough that you can see the solution before you've written a line. Then writing it. Running it. Watching it do exactly what you envisioned. That moment when the output just appears and it's right, it's genuinely hard to describe if you haven't felt it.

Then that piece connects to another piece. And then you're watching a whole system work, something you assembled, and you understand every part of how it fits together. Each piece a confirmation that the larger thing is real. And eventually you hand it to someone and they use it and they're just amazed that it works.

That's the difference between working ticket by ticket and actually understanding the system you're building. One produces output. The other builds something that lasts.

The coding skill is just the entry ticket.

What keeps you in the room is pattern recognition across problems you've never seen. Knowing when to push and when to wait. Understanding what people actually need versus what they're asking for. The willingness to stay curious when you could coast. Being able to start over when everyone's invested in the wrong direction.

The doom callers talk about replacement like code is the whole job. It's not. Code is the artifact. The job is figuring out what to build, why it matters, how it fits into someone's actual life, and then making it real despite everything that tries to stop you.

The uncertainty never left. New frameworks, new paradigms, new tools that make last year's expertise look outdated. Now AI is doing the same thing at a bigger scale.

Good.

If the only thing you bring is translating requirements into code, you were always going to struggle. Not because AI came along. Because that was never where most of the value came from.

The interesting part is what happens before and after the code. Judgment built from mistakes. Taste from years of shipping. Seeing what's missing. Knowing when to ship and when to keep going.

Those come from doing the work. From caring about it past the paycheck.

From remembering why we do this.