There is a version of me on this blog that is still true, but no longer complete.
If you read through the older posts, you will find someone very close to the craft: building things, experimenting, writing about side projects, and occasionally disappearing down a rabbit hole about old computers or some tiny technical detail that felt too interesting to ignore. That person is still here.
But I am not only that person anymore.
These days, I spend most of my working life helping teams build products across app and web. My title says engineering director, and that is accurate enough, but it does not fully capture how I think about the work. I still think of myself as a maker first and a leader second.
That is not because leadership matters less. It matters a lot. Helping teams do good work at scale is its own craft. Direction matters. Prioritization matters. Clear communication matters. Creating the conditions for good engineering matters. A team with the right clarity, trust, and momentum can do far more than any one individual contributor working alone.
Still, I have never lost the urge to make things.
I still like the moment when an idea moves from vague to concrete. I still like sketching something out, testing a thought in code, writing a rough draft, or following curiosity just far enough to see if there is something real there. Even when my role pulls me toward alignment, planning, and coordination, some part of me is always looking for the smallest useful thing that can be built next.
That tension is a big part of who I am now.
On one side, I care deeply about organizations, teams, and how good product work happens in practice. I care about how decisions get made, how strategy becomes execution, and how to create an environment where engineers can do thoughtful, sustainable work. On the other side, I still care about tools, experiments, prototypes, and the occasional side quest that exists mostly because making things is fun.
I do not see those sides as opposites.
If anything, they make each other better. Staying close to the craft makes me a better leader. It keeps me honest. It reminds me that software is made by people, not by roadmaps. It helps me recognize when process is useful and when it is just process. And leadership, at its best, has made me more aware of the bigger picture around the work: the trade-offs, the communication, the timing, the constraints, and the people involved.
So this blog should probably reflect that more clearly than it has in the past.
I still want this to be a place for writing about building things. But I also want it to be a place where I can write about the messy middle: engineering leadership, product development, ways of working, side projects, software and web experiments, and the practical reality of trying to keep a maker mindset while carrying broader responsibility.
Not a personal rebrand. Not a dramatic reset. Just a more accurate picture.
The old posts are still part of the story. They capture what I was paying attention to at the time, and I still like that. But going forward, I want the blog to sound more like the person I am now: someone who still likes to build, still follows interesting ideas, and also spends a lot of time thinking about teams, direction, and how good work actually gets done.
So consider this a small reintroduction.
I am still a maker.
I just spend a lot more of my time leading too.