On Building in Public
Why I decided to build this site in the open, and what I want to share along the way.
Most personal sites are polished artifacts — the final product with no trace of the process. This one is going to be different, at least in intent.
I work in software architecture and engineering leadership. A lot of what I do involves decisions that are only visible inside the organizations where they happen: the trade-offs we accepted, the patterns we rejected, the things that worked and the things that quietly didn’t. I want to write about those things — not the outcomes dressed up as case studies, but the actual reasoning.
This site starts small on purpose. A home page, a blog, a projects section, a way to get in touch. The code is on GitHub. The infrastructure is boring: Astro for the frontend, a .NET API, Azure Container Apps. Nothing clever. The interesting part is what I put in it.
My goal is to write one post worth reading per month. Not about trends or opinions manufactured for engagement — about problems I have actually encountered and thought about carefully. If that sounds useful to you, check back. If you want to start a conversation, the contact page is right there.