Why I moved away from a static portfolio and turned this website into a place for writing, context, and ongoing work.
For a long time, this website worked as a simple portfolio: a short intro, some experience, and a list of projects.
That format was useful, but it eventually became too static for the kind of work I actually want to show.
A portfolio is a snapshot. My work is not.
I wanted a place where the homepage could stay alive through writing, while the professional summary could remain easy to find in a dedicated /resume route.
This update started from a practical decision: separate the site into clearer jobs.
/blog acts as the archive./resume keeps the professional summary and downloadable PDF./projects remains available for selected work.That structure feels closer to how I actually use a personal website. Not everyone arrives for the same reason: some people want context, some want a resume, and some want to see how I think.
The old site was asking one page to do everything.
Now each route has a smaller responsibility:
This also makes the site easier to maintain. Updating a resume should not require rewriting the entire homepage, and publishing something new should not mean inventing a new portfolio section every time.
I do not want the blog to be a content machine. I want it to be a useful record of real work.
That means writing about:
If this site works well, it should feel less like a brochure and more like a working notebook with a professional front door.
This first version is mostly about structure.
The next step is keeping it active: updating the writing, refining the resume page, and letting the site reflect current work instead of old snapshots.
That is the main reason for the change.