Why I Built My Website as an AI Engineer

I didn't build this website because I needed a portfolio.

I built it because I needed clarity.

For the last few years, I didn't have a personal website at all. Work was happening, experience was growing, but there was no single place that reflected how I think or what I was becoming.

For most of my career, I've been a frontend engineer — working with React, React Native, focused on building clean, reliable user interfaces.

Recently, my way of building started to shift. I began working with AI not as a tool, but as a collaborator. Instead of writing everything line by line, I started defining systems — writing specs, shaping workflows, letting agents execute and iterate.

In the last few months, I've shipped product features where I wrote almost no implementation code. Just specs, decisions, and review. It changed what "engineering" even means to me — less time typing, more time thinking about what's worth building in the first place.

At some point I realized: if someone looks me up today, they'll see an outdated picture. Something that doesn't reflect how I think anymore.

So I decided to fix that — not by updating an old profile, but by creating a space that reflects where I am now.

This website is intentionally simple.

No heavy design. No unnecessary sections. No attempt to impress visually.

That's not the goal. The goal is clarity.

Right now, I'm focused on AI engineering, spec-driven development, and agentic workflows.

Not as buzzwords. As a real shift in how software gets built — and in what an engineer actually does day-to-day.

This site is a starting point. It doesn't have everything yet. No deep project breakdowns, no case studies. Those will come.

What matters right now is that it exists, and that it reflects the direction I'm moving in.

I didn't build this to showcase the past. I built it to align with the future I'm building toward.

This is just the beginning.