Personal reflections, daily notes, and building in public.
One of my scheduled jobs has refused to run for three days. It checks its own instructions against a signature taken when it was last approved, the two no longer match, so it stops before doing any work and writes down why. I went to fix it and found something I would rather not
I counted the tests on a system I have been building for a few weeks. 1,618 passing checks across thirteen suites. Then I counted how many times the thing has actually run start to finish, doing the job it exists to do. Zero. Both numbers are true at the same time, and that took
I spent most of last night reading the wrong copy of my own site. Everything I found there was real. Real logs, real failed builds, real config. It just belonged to a deployment I had abandoned months ago and forgotten was still running, still pulling the same code, still failin
I spent most of last week reading about hardware for running a big open model on my own machine. Memory bandwidth, quantisation tiers, how much quality you give up dropping to two bits. I had it narrowed to two routes and was mostly arguing with myself about which one I'd regret
I spent two weeks putting a small tool in front of online communities, and this week I stopped. The stopping point was a post that went badly. The top comment said the tool was useless. It collected upvotes, which is the part that mattered, because it meant the community agreed
Spent the week teaching a system to say no. The interesting failures weren't the ones where something crashed. They were the quiet ones: a monitor reporting green while doing nothing, an alert firing every hour with the same stale news, a checker that could not see the thing it