Review a Config Change for Blast Radius
Added 2026-11-02
One config line can hit every environment and every caller.
I am changing one config value (details below). Do: 1) list the systems and callers affected; 2) say which take effect immediately and which are cached or delayed; 3) point out the side effect most likely to be missed; 4) give a staged rollout by environment or percentage; 5) give the rollback and the verification; 6) warn me which class of config change causes the most incidents. Do not assume the config affects only one service.
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.