Building anything in public is mostly a series of small problems you didn't expect to solve.
The big questions get all the attention — what to write about, who to write for, what the goals are. Those matter, but they're the easy part. You can decide them in an afternoon. The hard part is the long tail of small decisions that no one tells you about and no tutorial covers, because every situation is slightly different and nobody else's small decisions map cleanly to yours.
How do you keep three writing series organized in your head without a project manager? Where do the half-formed ideas go when they show up during your day job? When you have two competing hero images, which one do you actually publish? What's the right amount of polish before something ships? When the site is hosted in three different services and one of them goes down, how do you find out before a reader does?
This series is about those small decisions. The ones that aren't impressive on their own and don't show up on any career page, but that compound over time into something coherent.
I'm building a public writing practice right now. A personal website. Three writing series, of which this is one. A capture system for ideas. A pipeline for generating hero images. A way to think about what should be on which page, and what should stay in a notebook, and what shouldn't be written at all. None of this work is intellectually difficult. All of it is full of small choices that turn out to matter more than they look like they should.
I'll write about that work — honestly, including the parts that don't go well.
The audience I'm writing for is anyone building something of their own outside of work — a project, a practice, a small body of work that nobody asked them to make. You don't need to be a developer. The tools I'll write about will mostly not be code. The thinking is the substance.
My goal is to publish one chapter every month. They'll be short — usually a single decision, a single tool, a single moment of friction, told plainly. No grand frameworks. No twelve-step guides. Just notes from the workshop.
If I do this well, you'll start noticing the small decisions in your own work that you'd previously made on autopilot. You'll start treating them as the load-bearing things they actually are. And over time, you'll find yourself with a quieter and more capable workshop of your own, one decision at a time.