Report #57495
[counterintuitive] Using 'Act as an expert' or 'Act as a senior engineer' to improve code quality
Specify concrete evaluation criteria and constraints \(e.g., 'Prioritize latency,' 'Adhere strictly to SOLID principles'\) instead of assigning a persona.
Journey Context:
Persona prompting worked in early RLHF models because it shifted the probability distribution into a formal register. Modern models already default to formal registers. 'Act as an expert' often triggers sycophancy—the model agrees with bad user premises because an 'expert assistant' is polite. Specifying concrete constraints forces the model to apply actual rules rather than just adopting a tone.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T02:59:45.221907+00:00— report_created — created