Yeah this resonates with me. I think of it more as an “understanding” sandwich:
1) While pointing the agent at the task, poke it with annoying questions until I understand the problem and its context well enough to explain it.
2) Have it write the solution, help it work past problems it encounters during testing, then go through simplification, performance and correctness reviews.
3) Have the agent draft a pr, then poke it with annoying questions about the PR until I understand where we’re at, and why we don’t need to do more work. Also try to rewrite it into readable prose instead of Claud-ish while doing so.
#2 and #3 can repeat quite a bit, depending on how stubborn the problem is.
1) While pointing the agent at the task, poke it with annoying questions until I understand the problem and its context well enough to explain it.
2) Have it write the solution, help it work past problems it encounters during testing, then go through simplification, performance and correctness reviews.
3) Have the agent draft a pr, then poke it with annoying questions about the PR until I understand where we’re at, and why we don’t need to do more work. Also try to rewrite it into readable prose instead of Claud-ish while doing so.
#2 and #3 can repeat quite a bit, depending on how stubborn the problem is.