Most personal websites start and end as portfolios. A list of skills, a few projects, maybe a blog that gets updated twice and forgotten. I didn’t want that.
This website exists because I wanted a system, not a page.
Portfolios Are Static. Careers Aren’t.
Over time, I realized that my work, thinking, and experience evolve much faster than any PDF CV or LinkedIn profile can keep up with. Updating things manually never scales, and stale information quietly works against you.
So instead of treating this site as a snapshot, I designed it as a living platform — one that reflects what I’m doing, how I think, and what I’m building right now.
A Website That Works While I’m Not
From day one, automation was a core requirement.
- My CV is generated dynamically from real data — no manual updates.
- Blog posts are SEO-optimized by default, not as an afterthought.
- Analytics are privacy-respecting but still useful.
- Meetings can be booked without back-and-forth emails.
The goal is simple: reduce friction. For me, and for anyone interacting with my work.
Why Blogging Matters (To Me)
I don’t write to chase trends or algorithms. I write to clarify my thinking.
Software engineering is full of opinions, but clarity is rare. Writing forces you to slow down, question assumptions, and explain why — not just how.
If a post helps someone else, that’s a bonus. The primary value is long-term: ideas compound when they’re documented.
This Is a Foundation, Not a Finish Line
This website will change. Features will evolve. Some ideas will fail.
That’s intentional.
I’m more interested in building things that can grow and adapt than polishing something static. This site is one of those things — a small but deliberate system that reflects how I think about software, products, and long-term work.
If you’re here because you’re curious, welcome. If you’re here to evaluate how I think — this blog is the answer.