Process ·
Small steps you can review
I split anything substantial into work packages small enough to review in one sitting. Each one ends with something I can open, test and judge before deciding what comes next.
This site is being built that way. Instead of one large rewrite, it has gone through a sequence of numbered packages: fixes and accessibility first, then self-hosted fonts, then the home page, then projects and notes. Each package ended with a complete, working copy of the site that I could preview locally before approving the next step.
Why it works
Mistakes stay small. When a step goes wrong, it goes wrong inside a small, well-understood change. Undoing it costs minutes, not days.
Review stays honest. A change you can read in one sitting is a change you will actually read. A large one tends to be skimmed and approved on trust.
Decisions arrive at the right time. Some questions don't need answers on day one. Which projects to describe publicly, or how much personal detail belongs on an About page, can wait until the package that needs the answer — and by then the answer is usually clearer.
It matters more with AI
An AI development partner can produce a lot of output very quickly. That is useful, but it moves the bottleneck from writing to reviewing. Small packages are how I keep up with what has been produced and stay accountable for what ships. I wrote more about that in the essay about building nihiramusic.in (opens in a new tab).
What a good package looks like
- A goal that fits in one sentence.
- A tangible deliverable — a working page, a script that runs, a document someone can read.
- A clear statement of what is not included this time.
- A check before moving on: preview it, test it, decide.
None of this is new. It is the same idea behind small pull requests and short iterations. Writing it down simply makes it easier to stick to when a project gets exciting and the temptation is to do everything at once.