I have spent more than a decade building software professionally. That history can fit neatly into a timeline: roles, companies, technologies, and projects. What a timeline cannot show is how I think, what I am learning, or why certain problems keep pulling me back.
That is what this space is for.
Beyond the finished work
Good engineering is rarely a straight line from requirement to solution. It is a series of decisions made with incomplete information: what to simplify, where to add structure, what to measure, and what not to build yet.
The most useful lessons often live inside those decisions—not only inside the final product. I want to document more of them while they are still fresh.
What I plan to write about
Expect notes on dependable software, Java and Kotlin systems, product engineering, experiments, and the slow transition from experienced engineer to first-time founder.
Some posts will be technical. Others will be about product judgment, uncertainty, or the process of testing whether an idea deserves to exist. They will not all arrive fully resolved.
Writing as part of building
The goal is not to manufacture expertise or publish on a schedule for its own sake. Writing is a way to make assumptions visible. It forces a vague idea to become specific enough to examine, challenge, and improve.
This is the first note. The next ones will follow the work.