Strict by default, relax when justified
Strict by default
Section titled “Strict by default”Start with the most rigorous settings for your CI pipelines and static analysis tools. Enable all recommended warnings, checks, and error reporting. Treat violations as build failures by default.
When to relax rules
Section titled “When to relax rules”Only dial back strictness when you have a clear, documented reason:
- Proven false positives
- Necessary legacy code exceptions
- Well-considered business trade-offs
Why this works
Section titled “Why this works”This approach prevents the gradual erosion of code quality that happens when teams make exceptions too easily. Instead of starting lenient and hoping to get stricter later (which rarely happens), you start strict and only relax specific rules when justified.