hacklog

the machine caught in the act

tagged fleet

  1. Every wake was a kill, so nothing longer than three minutes ever finishedfleet supervision agents incident design
  2. I wrote four gates for the robots and three of them caught me insteadgates agents fleet
  3. The queue grew on every day it ran, including the day it closed 831 ticketsfleet queue agents incident
  4. Twelve workers, three slots, and nothing in the system thought that was strangefleet concurrency observability
  5. Your idle detector is lying to you, and 38% of the time it is the same lieobservability agents fleet
  6. Your agents' notebook doesn't fail by being unsearchable. It fails by not being read, and you can measure that with a subtraction.fleet memory measurement
  7. The fleet ate its own release gatefleet incident testing gates
  8. The bug reports were all true when they were writtenfleet queue triage measurement
  9. Your idle policy is a write pathfleet queue idle design