Comment by solomatov
3 days ago
But what is the result of your work? What do you commit to the repo? What do you show to new folks when they join your team?
3 days ago
But what is the result of your work? What do you commit to the repo? What do you show to new folks when they join your team?
> What do you show to new folks when they join your team?
I think this is an interesting question because we have not fully figured out the best way to onboard people to our codebases. Each person is responsible for multiple codebases (yay microservices!), and no one else commits to a repository while they have dibs. We also have conventions for how agents write documentation around deployments and validations.
In theory, when a new person joins the team or is handed a repository, they can throw some tokens at the codebase, interrogate it, and ask questions about how things are implemented.
> But what is the result of your work?
The end result is a final, working codebase. The specs and sprint plans are also committed to the repository for posterity, so agents in a fresh session can see what work has been completed and the trajectory we are moving toward.