1 min lesson
Correctness is the contract
Rebuild the main list in "Correctness is the contract", then say what each item changes.
Step 1 of 2
Correctness is the contract
Every claim and every code block ships verified. One broken example or one stale flag and the reader assumes the whole post is sloppy, because they can no longer tell which parts you actually ran. In developer writing, correctness is not quality polish. It is the precondition for being read at all.
- Run every code block in a clean environment, not the messy one where it happened to work.
- Verify flags and field names against the current SDK or CLI, not your memory of last month's version.
- State your versions: "as of cursor-agent 0.x" ages gracefully where an unqualified claim rots silently.
- When you say "the agent does X," confirm it does X by reading the behavior or the source, not by trusting a model's summary of itself.
When they hand you a draft or a docs page to critique, lead with reader-job clarity ("which of the four doc types is this trying to be?"), then hunt the unverified claim. Pointing at one sentence and asking "did you run this or did the model tell you it works?" is exactly the taste-plus-truth-seeking signal the role screens for.
Learn more
Optional practice
Practice: Correctness is the contract
QYou're writing a Cursor blog post and reach for the sentence "Cursor's powerful agent handles complex refactors." Why does this hurt you with a developer audience and what do you write instead?