Your AI agents need an HR department
When one assistant becomes several, the hard part is the roster: a role, a trial, one owner per task, access that ends with the role, and a record of why one was retired.
Mario Ruiz Sánchez · Senior Software Engineer in Reykjavík
Commands, old machines, and experiments. Agents and APIs, an MSX that spoke in sound, and the history and language around the tools.
When one assistant becomes several, the hard part is the roster: a role, a trial, one owner per task, access that ends with the role, and a record of why one was retired.
A token quote in the queue is a guess about one message. A coding task is a loop of context, tools, retries, and red tests.
Coding with AI is killing the diversity of programming languages. Not by banning anything, but by making the popular choice a little easier every day.
Every chat starts by reading the same file. If that file is long and stale, every answer starts a little wrong.
A ticket in prose is advice. A failing test is an order. When an agent writes the code, only the second one holds.
Writing poetry taught me that every line has to earn its place. Code is the same craft, and with AI writing the words for us, we are quietly letting it go.
Which line in that diff is worth reading, and why the agent must not be the one who updates the suite.
If an agent paraphrases a check people already run in Slack, you get two answers for one command.