A Control Plane for a Personal GitHub Account
I have around 120 repositories under my personal GitHub account. Some are active, most are dormant, and all of them rot at the same rate. Dependencies drift, GitHub Actions pin to versions that get …
Building your own tools
When software has exactly one known user, it can drop its whole configuration layer. What that changes, and what it costs to run a personal estate of tools: release pipelines, CI budgets, account automation and agent safety.
Building Your Own Tools
Configuration is the tax you pay for not knowing who your user is. It has always been priced into the cost of building software, so we stopped noticing it was there. Build something for exactly one …
Cadence is a budget line: what scheduled automation cost a private repo
A cron line looks like a latency setting. 0 * * * * reads as “check every hour, so nothing waits long.” In a private repository it’s also a purchase order, and it reorders every hour whether or not …
Letting an agent read your mail: split the reader from the network
Every email in your inbox was written by someone else, and most of them were written by someone you’ve never met. Hand that inbox to a model and you’ve handed it several hundred prompts from …
Stop declaring what you can already read (myspec)
Every time you ask someone to tell your tool something it could have found out, you’ve created a second copy of a fact. Second copies drift. In an agent’s toolchain there are a lot of facts, and until …
The release pipeline four tools kept reinventing (release-kit)
Every tool I build for myself needs the same last mile: binaries for my machines, a Homebrew formula, something bx can run. That’s the same work each time, and I kept writing it again for each tool. …