ALL-PERF1002 · optimization_justification
Judge whether an optimization earns its complexity.
This is a contextual rule for all languages. Read its implementation.
Definition
Section titled “Definition”Compare before and after measurements, workload relevance, correctness, resource tradeoffs, readability, and maintenance cost. Missing baseline or profile requires uncertainty.
Evidence
Section titled “Evidence”Findings cite benchmark results, profiles, correctness checks, and complexity changes.
Exceptions
Section titled “Exceptions”Hard resource limits can justify small gains when the constraint and margin are explicit.
Examples
Section titled “Examples”A simpler implementation that cuts peak memory by half is supported. A cache added without a
measured bottleneck is unsupported or uncertain.
References
Section titled “References”- Cites “Structured Programming with go to Statements”
- Cites “Systems Performance”
- Cites “A Philosophy of Software Design”