The site should stop feeling like a polished resume page and become a public working surface.
Not a corporate portfolio. Not a devrel blog. Not "look at me, I use cloud words."
The point is to make visible how I think about systems, automation, observability, project experiments, and engineering doctrine. That means showing unfinished work honestly. A repo can be useful even when it is not shipped, as long as the page says what the project is testing, what is real, what is fragile, and what I am learning from it.
This is partly a time capsule and partly a source of record. I want to be able to look back and see what I cared about, what I understood, what I misunderstood, and how my thinking changed.
The recurring theme is systems. I do not like busywork for its own sake. I can do the mundane work, but if a process keeps repeating, hiding state, or making people guess, my brain starts looking for structure.
Automation is part of that. The deeper thing is wanting the system to become legible.