This might help, but tell Claude to do Test Driven Development [TDD] which will require each feature/function/etc.to have a test case and a pass before it can exit the worktree before a PR.
Also look into graphify which does a bit of “explain what this does” and makes things very easy to describe the code in a systematic way. AST is here again.
I’m having success with an agentic orchestration model that doesn’t move on unless they pass the tests. And if they fail they hand off to a smarter model. I have to guide it and sometimes ask basic questions about why we’re trying to load docker locally when I have guthub actions to do it, but if you know that much you can just poke it with a stick occasionally. The graph is updated and I have records for design decisions and reports on failure as well as tests to pass.
This is definitely a different approach and I can easily see how some people don’t get it; and it’s probably tied to doing things the hard earned way. Less developer and more TPM in terms of mindset.
I think throughput [lines of code, commits, PRs, beans, etc] is a worthless metric, velocity means speed + direction. A poorly guided version is just scattered all over, make it work and that’s it, until the next round of changes.
This might help, but tell Claude to do Test Driven Development [TDD] which will require each feature/function/etc.to have a test case and a pass before it can exit the worktree before a PR.
Also look into graphify which does a bit of “explain what this does” and makes things very easy to describe the code in a systematic way. AST is here again.
I’m having success with an agentic orchestration model that doesn’t move on unless they pass the tests. And if they fail they hand off to a smarter model. I have to guide it and sometimes ask basic questions about why we’re trying to load docker locally when I have guthub actions to do it, but if you know that much you can just poke it with a stick occasionally. The graph is updated and I have records for design decisions and reports on failure as well as tests to pass.
This is definitely a different approach and I can easily see how some people don’t get it; and it’s probably tied to doing things the hard earned way. Less developer and more TPM in terms of mindset.
I think throughput [lines of code, commits, PRs, beans, etc] is a worthless metric, velocity means speed + direction. A poorly guided version is just scattered all over, make it work and that’s it, until the next round of changes.
But it’s definitely a different game now.