Articles
Technical writing on behavioral regressions, code review blind spots, and why certain bugs only show up in production.
gRPC .NET PR #2531 Analysis
Behavioral risk signals in a fundamental RPC framework pull request.
Read article →
StackExchange.Redis PR #3028 Analysis
Behavioral change risk in a critical infrastructure library pull request.
Read article →
Google API PR #3150 Analysis
Behavioral risk analysis of a major Google API library pull request.
Read article →
log4net PR #201: 3,753+ Risk Signals in a Major Enterprise Refactor
Large-scale logging framework refactoring introducing thousands of behavioral changes across multiple code paths.
Read article →
Enterprise Case Studies: Real-World Behavioral Change Risk
Collection of real production failures, missed code reviews, and test blind spots. How companies are using behavioral analysis to catch regressions that escaped traditional CI/CD.
Read article →
Beyond SonarQube: A Behavioral Alternative to Code Smell Detection
Why linter rules and code smells miss behavioral regressions. A case for deterministic behavioral analysis as a gating criterion instead of counting violations.
Read article →
How Azure SDK PR #57223 Introduced 6,650+ Unique Risk Signals
Azure SDK PR #57223 generated 6,650+ unique behavioral risk signals across 3 framework versions. See why traditional tools missed them.
Read article →
A "Performance Improvement" PR Introduced 11 Block-Level Risks
Jellyfin PR #16062 escaped code review despite introducing 11 block-level risks. Discover why traditional tools miss behavioral regressions.
Read article →
What Is Diff-Based Analysis?
Diff-based analysis evaluates only what changed in a commit. Why that scope is the right unit of risk for pre-commit checks.
Read article →
A Formal Framework for Behavioral Change Risk
A structured taxonomy for behavioral, contract, concurrency, and side-effect risk in code diffs.
Read article →