Conflict Resolution

Lead With the Error, Not the Hunch

Inspired by Episode 2: The Bug That Wasn’t a Bug

In Episode 2, Paul says the function is crashing; Nova reviews the code and declares it perfect. Meanwhile the terminal shows 47 errors that nobody pasted into the conversation.

The fix

  • Paste the exact error and the full stack trace, not a summary of it.
  • Include how you ran it: the command, inputs, and environment (versions, OS, config that matters).
  • Say what you expected versus what happened.
  • Share the code the trace points at, not just the function you suspect.

Template

Command: npm run import -- data/users.csv
Expected: 1,200 users imported
Actual: crash after ~40 rows

Full error and stack trace:
<paste>

Relevant file (src/import/processData.js):
<paste>

An assistant can only debug what it can see. Show it the evidence.

More lessons from Episode 2