Why I'm evolving from software engineer to founder-engineer

For a long time, I introduced myself primarily as a software engineer. That identity is still true, and it still matters a lot to me. But it is no longer the full picture.

Today, the way I think about my work is broader. I am more interested in building technology businesses, products, and systems, with software as one of my main tools for doing it well.

This is not a departure from engineering

Engineering has shaped how I think: precision, curiosity, systems, craft, and a desire to understand how things actually work. I still love building with software. I still care about product quality, technical decisions, and the discipline of execution.

What has changed is not my respect for engineering. What has changed is the frame around it.

I no longer want to think of code as the final destination. I want to think of it as leverage: a way to create products faster, learn faster, operate better, and build stronger businesses.

What changed

Over time I became more interested in questions that sit beyond implementation.

What problems are worth solving?
Who are they worth solving for?
What kind of business can grow around a product?
What systems help a small team move with clarity and speed?
How can software, AI, and automation multiply execution instead of just adding complexity?

Those questions pulled me toward product thinking, business design, and company building.

I still enjoy shipping code. But I am increasingly motivated by the larger process: identifying opportunities, shaping the right product, building the operating system around it, and turning ideas into durable ventures.

Software as leverage

One of the reasons this shift feels exciting to me is that software has never been more powerful as a leverage tool.

A small team can now build, automate, test, distribute, and learn at a speed that used to require a much larger organization. AI makes this even more interesting. Not because it replaces clear thinking, but because it can amplify it when used well.

That is the kind of work I want to do more of: using technology to create advantages in execution, decision-making, operations, and learning.

In other words, I care less about software for its own sake, and more about what software makes possible.

What this site will become

This website is changing with that direction.

It will be less of a generic personal blog and less of a pure engineering portfolio. It will become a home for documenting what I am building, what I am learning, and how my thinking is evolving as a founder and builder.

You can expect writing around topics like:

building products and businesses
founder lessons and operating principles
systems, leverage, and automation
software and AI as tools for better execution
the realities of turning ideas into ventures

I want the site to feel closer to my actual work now, not just to an earlier version of my career.

What stays the same

Even though the framing is changing, a lot of the foundation stays the same.

I still care deeply about quality. I still believe in thoughtful execution. I still like the details, the craft, and the process of turning ideas into working things. I still want to keep learning across engineering, business, systems, and strategy.

The difference is that I now see all of those pieces as part of a larger mission: building meaningful companies and useful products.

The next chapter

This is the first step in refreshing the public side of this website.

I am cleaning up the writing, sharpening the narrative, and making the site more honest about what I am actually trying to do. That means fewer filler posts, more signal, and a clearer point of view.

If you are interested in products, businesses, software, AI, systems, or the founder journey, this is what the next chapter of the site will be about.