Conflict Resolution

Second Opinions Done Right

Inspired by Episode 8: It’s Just Context

You’re reading a subscriber article on a free read. You have 1 free read left. Subscribe free for the whole archive.

Paul gets a second opinion in Episode 8; it suggests couples therapy. A second model can be genuinely useful as a reviewer. The trick is to give it the work, not the drama.

How to ask for a review

  • Share the artifact: the diff, the design or the error. Skip the conversation history.
  • Don’t reveal which answer you prefer. Ask it to evaluate, not to agree.
  • Ask for specific risks: bugs, edge cases, security issues, simpler alternatives.
  • Verify disagreements yourself: when two tools disagree, the tests decide.
Review this diff as a senior engineer. List bugs, unhandled edge
cases and security concerns, most serious first. If it's fine, say so.

<diff>

And mind what you paste: the same data rules apply to the second tool.

More lessons from Episode 8