Lessons / Part 3 of 6
3
Part 3 of 6, 7 lessons
Set the boundaries
Give agents hours of freedom without giving them your authority.
I leave agents running for five or six hours. That only works because the limits are written before I go, and because some of them cannot be argued with. These lessons are the written contract for a run, and the fences that came out of things going wrong.
The lessons, in order
- 07More freedom needs more structureThe longer an agent runs alone, the more has to be written down first.
- 11Preparing an AFK runFive things I do before I walk away.
- 13Anatomy of an AFK runIt starts with a contract and ends at a gate. Nothing in between merges without my yes.
- 16Keep secrets out of sightAn agent can read files, terminal output and process details. A secret can be in all three.
- 17Never test against production dataAgents need somewhere they can break things.
- 18Local means localA tool called local reached production, and spent money doing it.
- 19The database must be ready firstCode that deploys by itself must never arrive before the tables it expects.