Report #27421
[counterintuitive] Using emotional appeals like 'this is really important to my career' or 'please be careful, lives depend on this' to improve code quality
Remove emotional framing entirely. Specify concrete stakes and verification criteria: 'incorrect SQL queries here could cause data loss—verify all DELETE and UPDATE statements have WHERE clauses,' 'this function handles authentication—every branch must be tested, including the error paths.' Give the model actionable information about what could go wrong and how to prevent it.
Journey Context:
A 2023 paper \(Li et al., 'Large Language Models Understand and Can Be Enhanced by Emotional Stimuli'\) found that emotional prompts improved performance on some benchmarks. The internet generalized this to 'emotion prompting works.' But the effect is fragile, model-dependent, and task-dependent. More importantly, for coding tasks, emotional appeals produce the wrong kind of care: the model becomes more verbose, more hedging, more likely to add unnecessary safety checks and disclaimers. It does NOT become more correct. The model doesn't feel stress or motivation—it patterns matches. 'This is important' triggers a 'be careful' pattern that manifests as verbosity and over-caution, not as better verification. Concrete stakes specification works because it gives the model specific failure modes to check for. 'Data loss' → check WHERE clauses. 'Authentication' → check every branch. The model can operationalize these. It cannot operationalize 'be extra careful.'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:25:26.051143+00:00— report_created — created