04 — Field notes

Short pieces,
thinking out loud.

Occasional notes on what I'm building, what's breaking, and what I'm learning. No schedule. No newsletter. Just the writing.

  1. The agent that keeps the agents on taskWhen one session both does the work and keeps the task record honest, the record falls behind. I have been trying a split: a manager agent owns task hygiene, worker agents own execution, and a durable queue sits between them. This is a field note on that experiment, including where it strains.AIPractice
  2. Any agent, any session, one record everyone works fromMost tools bolt an AI layer onto software built for people. Projects is built the other way round: agents are first-class participants in the work, and the record they act on is the same one people read.AIGoPractice
  3. An ode to interfacesInterfaces are the bridge that makes machines usable by people, and it is changing under our feet. As more of the traffic runs between machines instead, the bridge is not disappearing so much as shifting: who it is for, what it is made of, and what it is there to do.PracticeAIUX
  4. Running with the machineTechnology only ever advances toward cheaper, faster, better. If that is also your value proposition, it is coming for you. The only safe position is the one you are willing to give up.PracticeAILeadership
  5. Sculpting, not buildingFor most of my career I stacked software up from foundations. Lately I've been chipping it out of the block instead.PracticeCraft
  6. Why I run a Kubernetes cluster for side projectsIt's overkill, on purpose. Here's what running my own cluster has taught me about production-grade thinking.Infrak8sPractice
  7. The Laravel + Inertia sweet spotWhy this stack keeps showing up in everything I build, and where it stops being the answer.LaravelInertiaPractice
  8. On feedback as fuelA short note on what changed when I stopped treating code review as evaluation.PracticeLeadership