1 min lesson
Match the register to a developer
Put this idea into your own words: "Cut the corporate softeners and write the way a competent colleague would explain it across the desk."
Step 1 of 3
Match the register to a developer
These users write code for a living. They want the exact version, the exact flag, the exact log line and they find padding insulting. Cut the corporate softeners and write the way a competent colleague would explain it across the desk.
Learn more
Advanced table
The right column resolves and reassures in the same breath
- Fluffy / generic
- "Please make sure your app is up to date."
- Precise / technical
- "This is fixed in 1.2.4 - Cursor → Check for Updates or grab the build from the changelog."
- Fluffy / generic
- "Try clearing your cache and restarting."
- Precise / technical
- "Delete the index cache: quit Cursor, remove the workspace's .cursor/index folder, relaunch to force a reindex."
- Fluffy / generic
- "We apologize for any inconvenience this may have caused."
- Precise / technical
- "This one's on us - the 1.2 indexer regressed on monorepos. Here's the workaround while we ship the fix."
- Fluffy / generic
- "Our team is aware of the issue."
- Precise / technical
- "Reproduced and filed as a P1; Eng is on it. I'll post the fix version in this thread."
| Fluffy / generic | Precise / technical |
|---|---|
| "Please make sure your app is up to date." | "This is fixed in 1.2.4 - Cursor → Check for Updates or grab the build from the changelog." |
| "Try clearing your cache and restarting." | "Delete the index cache: quit Cursor, remove the workspace's .cursor/index folder, relaunch to force a reindex." |
| "We apologize for any inconvenience this may have caused." | "This one's on us - the 1.2 indexer regressed on monorepos. Here's the workaround while we ship the fix." |
| "Our team is aware of the issue." | "Reproduced and filed as a P1; Eng is on it. I'll post the fix version in this thread." |
The right column resolves and reassures in the same breath; the left column does neither.
Over-apologizing reads as weakness to a technical user. A wall of "so sorry, truly sorry, apologies again" signals you don't have a fix. Acknowledge once, own it cleanly, then demonstrate competence. Ownership and a working next step de-escalate far better than effusive sorries.
"Thanks for the detailed report - you're right that Tab went quiet after 1.2 and I can reproduce it. It's an indexing regression on large repos, not something on your end. Quick unblock: reindex by quitting Cursor, deleting .cursor/index in the workspace and relaunching. I've filed this with Eng as a P1 and I'll post the patched version in this thread. If the reindex doesn't bring Tab back, send me the output of the Cursor → Developer → Toggle Logs panel and I'll dig in."
In the written exercise, narrate your structure before you write: "I'll acknowledge the specific failure, give the workaround up top, then set a timeline." Then deliver it. Reviewers love seeing the candidate who treats a support reply as a designed artifact rather than a vibe.
Learn more
Optional practice