Review a Feature for Rollback Cost
Added 2026-11-04
Before shipping, ask how hard it is to turn off.
We are shipping a feature (plan below). Estimate rollback cost: 1) what irreversible data the feature creates — messages, orders, state changes; 2) how that data is handled on rollback; 3) whether disabling requires code or config, and how long it takes; 4) whether some users already use the feature and what rollback does to them; 5) one design change that lowers rollback cost; 6) judge whether a full rollout is appropriate. Do not only discuss bug risk.
Site original
Chinese original
How to use
回滚成本高的功能，应该小步上线或做得可开关。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.