I’ve been asking myself a lot of questions lately about what I want to say and how to say it. But when I sat down to write my first post, the answer was obvious — start with the thing that defines you.

Because after 10+ years in the tech industry, my daily experiences have started to feel exactly like this. And apparently, the only logical response is to write about them.

And the first thing that defines me as a tech person is this: I am a Software Engineer. Not a developer, not a coder, not an architect. An engineer.

It might sound like a trivial distinction. It isn’t.

So what’s the difference?

A software developer writes code. Often very good code. Usually in a specific language, within a familiar framework, solving problems they’ve seen before. There’s real skill in that — don’t get me wrong.

A software engineer is something different. An engineer is a problem solver first. The language, the framework, the tooling — those are just instruments. Give an engineer an unfamiliar stack, a new domain, a constraint they haven’t faced before, and they’ll find a way. Not because they know everything, but because they know how to think.

It’s flexibility. It’s being perceptive — reading between the lines of a problem before writing a single line of solution. It’s being oriented toward outcomes, not just output.

And here’s the part that took me years to accept: it’s also a matter of personality.

You can teach someone a programming language in weeks. You can’t as easily teach someone to be comfortable with uncertainty, to thrive in ambiguity, to instinctively ask “but what are we actually trying to solve here?” before diving in.

I’d like to say this mindset can always be developed — and sometimes it can. The right environment, the right challenge, the right mentor at the right moment can unlock something in a person that wasn’t visible before. I’ve seen it happen.

But I’ve also seen the other side. People who are excellent within clear boundaries, who do their best work when the problem is well-defined — and no amount of support or challenge seemed to shift that. And honestly? That’s not a failure. Not everyone needs to be an engineer. The mistake is expecting everyone to become one.

Now, where does AI fit into all of this?

In a world where things change week to week — where new models, new tools, new paradigms appear faster than most teams can absorb them — the engineer’s mindset isn’t just useful. It’s essential.

AI is not the end of the engineer. It’s yet another tool. A powerful one, yes. One that will change how we work, absolutely. But engineers have always adopted new tools and adapted. That’s the whole point.

The question isn’t whether AI will replace software engineers. The real question is whether you have the kind of mind that sees AI as a constraint — or as an instrument.

And if you’ve read this far, I suspect you already know which one you are too.