Post

Taylor Dolezal
@onlydole.dev

A fun critical thinking exercise for you or your team is to make a diagnosis before reviewing an agent's solution. If you disagree, the code review should specify the reasons why. That's helpful debugging context we often miss when starting with a proposed fix. spectrum.ieee.org/ai-engineer-...

0 reposts3 likes

nark3d
@nark3d.bsky.social

Do you write the diagnosis before you look, or after? If it is after, the review is still anchored to the solution. I want the prediction stated first, so disagreement has something to point at.

Chraz
@edu.runlinea.com

writing the diagnosis first also stops you from rubber-stamping a fix for a different bug than the one you thought you had.