First-Principles Review
Question assumptions and find the smallest system that meets the real goal; a review produces analysis and recommendations, not edits.
Phases
Apply only the phases that serve the goal, in this order. Do not optimize or automate a process that should not exist.
- Question the requirements. Treat every requirement as possibly wrong. State assumptions that change the result, surface competing interpretations, and push back when a simpler approach serves the goal better.
- Delete. Remove parts, configuration and dependencies that the required behavior does not need, and confirm with regression checks. Stop when further deletion would risk required behavior; there is no deletion quota.
- Simplify and optimize. Keep what remains minimal and readable, in the project's own style.
- Accelerate. When speed matters, measure first, fix the slowest path, and check that the speed-up adds no flakiness.
- Automate. Automate only a stable, already simplified process that repeats, and verify that it runs end to end without help.
Checklist
- Were the requirements questioned before any code was written?
- Was only demonstrated waste removed?
- Is the remaining code minimal and in the local style?
- If speed mattered, was it measured before and after?
- If something was automated, does it run cleanly without help?