GoKawiilDeveloper Blog Revives 'CRAP' Metric for Code Quality Reviews
A technical blog post reintroduces CRAP (Change Risk Anti-Patterns), a code-quality metric that combines cyclomatic complexity and test coverage to flag risky, poorly tested code. The author traces its origins and argues teams should apply it as a practical check during software projects.
GoKawiil's interpretation of the reporting above, not reported fact.
As software projects scale, unmonitored complexity and thin test coverage quietly accumulate technical debt that later causes costly bugs and slow delivery. Reviving a simple, quantifiable metric like CRAP gives engineering teams an accessible tool to catch risk early without adopting heavier, more complex quality frameworks.
- CRAP metric combines code complexity and test coverage to estimate risk.
- The post revives an older concept for modern development teams.
- Simple metrics can help prioritize which code needs more testing or refactoring.
Clean Code by Robert C. Martin — If you're pondering how much code out there is truly 'crap,' this book is the classic guide to writing maintainable, readable software. It's a great practical companion for developers wanting to apply real craftsmanship principles to their own projects.
See Clean Code by Robert C. Martin on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.Source: testing.googleblog.com — Posted Alberto Savoia, 2026-09-16
Published there as: “Code Is Crap”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.