What I built, what broke, and the evidence that changed the next decision.
No spam. No marketing. Just the writing.
Rebuilding a system sounds like repeating the build. It rarely is. The first version accumulated decisions in the order I encountered them. A rebuild asks me to reproduce the result after that order, and much of the reasoning behind it, has disappeared.
A work session usually ends before the work does. The clock wins, attention gets thin, or the next obligation arrives. That’s normal. What causes trouble is leaving an unfinished system in a state that only makes sense to the person who has been staring at it for three hours.
An agent can receive instructions from almost anywhere. A chat message describes the task. A scheduler supplies parameters. A repository contains conventions. A wrapper adds defaults. A saved prompt contributes another set of rules. Each source is convenient in isolation.
One of the local automations I value most doesn’t have a dashboard. It watches a folder, waits for a file to finish arriving, applies a predictable transformation, and places the result where the next ordinary tool expects it.
The first five minutes of an incident are rarely long enough to diagnose it. They are long enough to damage the evidence, widen the uncertainty, and create three competing versions of what happened.
Household chores are a brutally honest queueing system. Work arrives from ordinary life, the machines have fixed capacity, and completed-looking steps have a habit of producing another pile somewhere else.
A paper notebook beside infrastructure looks a little sentimental until the infrastructure is the reason the digital notes aren't available.
A restart is satisfying because it produces motion. The process stops, the process starts, and the terminal returns a clean status. That can be exactly the right repair. It can also leave the system holding the same bad state, an unprocessed queue, and several users who are still refreshing a bro...
The browser is where all the private agreements in a web system become one public experience. A button carries the wrong label. A request leaves with the wrong shape. A response arrives correctly but never changes the screen. Each layer may look reasonable by itself, while the person using the pa...
Convenience layers are easiest to add when the underlying tool is almost pleasant. A desktop launcher can remember a model command. A web panel can turn flags into toggles. A helper script can choose ports, directories, and defaults so I don't have to. The first use gets shorter, which is real va...