Change & Complexity Defects
Defects caused by the act of changing existing code. The larger the change and the longer it lives outside trunk, the higher the risk.
less than a minute
These defects are caused by the act of changing existing code. The larger the change and the longer it lives outside trunk, the higher the risk.
| Issue | Earliest Detection (Automation) | Automated Detection | Earlier Detection with AI | Systemic Prevention |
|---|---|---|---|---|
| Unintended side effects | CI | Automated test suites, mutation testing frameworks, change impact analysis | ▲ Reason about semantic change impact beyond syntactic dependencies; automated blast radius analysis | Small focused commits; trunk-based development; feature flags |
| Accumulated technical debt | CI | Complexity trends, duplication scoring, dependency cycle detection, quality gates | ▲ Identify architectural drift, abstraction decay, and calcified workarounds | Refactoring as part of every story; dedicated debt budget |
| Unanticipated feature interactions | Acceptance Tests | Combinatorial and pairwise testing, feature flag interaction matrix | Reason about feature interactions semantically; flag conflicts testing matrices miss | Feature flags with controlled rollout; modular design; canary deployments |
| Configuration drift | CI | Infrastructure-as-code drift detection, environment diffing | Current tooling sufficient | Infrastructure as code; immutable infrastructure; GitOps |
Related Content
- Defect Sources - full catalog overview and how to use it
- Testing - testing types and best practices
- Anti-Patterns - patterns that undermine delivery performance