I have wanted to write for a long time, but I kept pushing it aside. There was always something else to ship first.
The reason I kept coming back to it is simple: I have strong ideas about engineering, delivery, and quality, and I want to contribute those ideas back to the community.
This is the same reason I started public speaking. It scared the living hell out of me in the beginning, and to be honest it is still nerve-wracking most of the time. I started small with company events, then moved to meetups, and eventually to conferences.
Writing is the same pattern for me now: start small, iterate in public, and improve with every post. I do not expect every post to be perfect. I expect to get better by writing more, and by doing it in public.
I also want this to be useful, not performative. You will not get polished thought leadership fluff here. You will get real decisions, real tradeoffs, and things that actually work in day-to-day software work.
I optimize a lot by nature, and that can stay trapped in my own projects if I do not write it down. This blog is my way of making those lessons reusable for others.
The plan is simple: write when there is something worth saying, keep it practical, and keep it honest.
If that sounds useful, stick around.
If you want to see how this writing ties into my workflow, read I and AI.