Welcome — and what this space is for

#Not only a developer blog

I have spent eight years building software, most of it on the web, currently leading frontend for a suite of crypto applications with a great team. So yes — a fair share of what lands here will be technical.

But I did not want a blog that only holds engineering. The writing I keep coming back to from other people is rarely the tutorial. It is somebody thinking in public: about how teams actually work, about the gap between the architecture diagram and the thing running in production, about what it costs to be the person who says "no, let's do it properly."

So this is a personal space. Ideas, opinions, the occasional argument with my past self. Some posts will have code. Some will not.

#What to expect

A few things I already know I want to write about:

• Decisions, not tutorials. There are enough posts explaining what a tool does. Fewer explain why someone picked it over the alternative, and what that choice cost six months later.
• The parts nobody documents. Technical leadership, mentoring, the work of turning a vague business ask into something an engineer can actually build.
• Things I got wrong. These tend to be the most useful ones to read, and the least comfortable to write.

#On frequency

I am not going to promise a schedule I will not keep. I have a few drafts already in progress and more articles coming in the next days. They will arrive when they are worth reading rather than when a calendar says so.

If any of that sounds interesting, the RSS feed is the honest way to follow along — no newsletter, no signup, no tracking.

Thanks for being early.