David White
Product and Engineering · Implera
Works on product and engineering at Implera. Writes about code quality, testing practices and keeping dependencies healthy in fast-moving codebases.
Articles by David White
Codebase Health Monitoring: A Practical Guide
Codebase health monitoring tracks quality signals continuously so regressions surface early. Learn the signals, cadence, and alerts that matter.
7 Code Quality Metrics Every Engineering Team Should Track
From test coverage to cyclomatic complexity, these seven metrics give engineering teams real visibility into codebase health.
What Is a Codebase Health Score?
A codebase health score distils complex quality data into a single number. Learn how scores are composed, why they help, and their limits.
The Hidden Cost of Skipping Code Reviews
Skipping code reviews saves time today but creates costly problems tomorrow. Learn how bugs, knowledge silos and security gaps compound over time.
Why Your Test Coverage Number Is Misleading
High test coverage does not guarantee good tests. Learn why coverage metrics can be misleading and how to use them as one signal among many.
A Practical Guide to Managing Technical Debt
Technical debt is inevitable but manageable. Learn how to identify, prioritise and pay down debt without stopping feature work.
Security Patterns Every Developer Should Know
Common security anti-patterns in web codebases and how to fix them, from committed secrets to SQL injection and CORS misconfiguration.
Keeping Your Dependency Supply Chain Healthy
How to manage dependency sprawl, lockfile hygiene, transitive vulnerabilities and licence compliance in modern codebases.
CI/CD Quality Checks That Actually Work
Most CI quality checks get ignored or bypassed. Learn how to design checks that teams respect with fast feedback and clear thresholds.
How to Measure Codebase Maintainability
Maintainability is hard to quantify. Learn the concrete signals that reveal whether a codebase is easy or hard to work with over time.
What Makes a Good Quality Gate?
Quality gates must balance strictness with developer experience. Learn how to set thresholds, get buy-in, and improve standards over time.