My rules for using Agents
I find agent to be a useful tool for coding, GitHub, and Slack. But like any tool, there’s some degree of skill necessary to wield them effectively and not hurt others.
When unguided, habits emerge that make code harder to maintain, communication harder to read, and collaboration thinner — which contribute to the collapse of a software team if left unresolved
My concern here is practical: are we using agents in ways that help us build good software together? These are the standards I’ve set for myself across my time with them across the past year or so:
Optimise for readability and clarity
- Short, direct sentences. Dotpoints with spacing
- No unguided slop essays
- Particularly in PR descriptions
- Your time saved must not become someone else’s reading burden
- Aim to ask good concise questions that encourage constructive discussion
- Sanitise all LLM-isms in output
- Otherwise it’s frustrating to read, and gives the wrong impression
- Short, direct sentences. Dotpoints with spacing
Keep work focused and reviewable
- No massive, unfocused PRs
- Split changes into coherent pieces and explain their purpose
- Remove unnecessary guff before asking for review
- No massive, unfocused PRs
Listen to people directly and stay engaged with people
- Never delegate the act of listening
- Read and consider their input yourself
- Review all agent-drafted responses before sending it
Mark what agents helped create
- Whether assisted or generated verbatim, make that involvement clear
Own and understand what you submit
- Read the code, PR description, review reply, or message
- Be able to explain it and defend it
- Attribution doesn’t transfer responsibility
- Go beyond being able to explain the output
- Develop your own understanding and judgement
- Prevent alienation and deskilling
Always verify
- Check the behaviour, claims, and sources
- Add your own correct, relevant citations.
- Open the links and confirm they support what you’re saying
- Declare what hasn’t been checked.
Give agents clear boundaries
- Agree on the goal, scope, and decisions that need human input
- Agents must always ask before changing tests
- Discuss significant changes with the people affected before starting.
Reply to this post by email blZake@proZbableodyssey.blog (remove Z characters) ↪