Articles
Technical writing on behavioral regressions, code review blind spots, and why certain bugs only show up in production.
Can AI Code Review Tools Ever Be Deterministic?
Exploring the difference between helpful AI review and trustworthy engineering controls. Why determinism matters more than you think.
Read article →
The Asymmetry of Change: Why Your Tests Are Looking the Wrong Way
Why passing tests don't guarantee correct behavior. How diff-scanning can close the gap between code changes and test validation.
Read article →
CodeRabbit Alternative: Deterministic Pull Request Risk Analysis
A buyer-focused comparison for teams evaluating AI pull request reviewers and deterministic PR risk analysis before merge.
Read article →
Best Code Review Tools for GitHub
A GitHub-focused guide to choosing code review tools across human review, AI assistants, security scanners, static analysis, and PR risk gates.
Read article →
Automated Code Review Tools for GitHub Pull Requests
How GitHub teams should choose automated code review tools for PR comments, required checks, Actions workflows, and deterministic merge protection.
Read article →
CI Quality Gate for Pull Requests
A practical framework for designing CI quality gates that block risky pull requests instead of only enforcing style, coverage, and known vulnerabilities.
Read article →
What Is Pull Request Risk Analysis?
Pull request risk analysis evaluates how a diff changes behavior, contracts, tests, runtime safety, and production blast radius before merge.
Read article →
Best AI Code Review Tools for Pull Requests
How to evaluate AI code review tools by evidence quality, repeatability, CI fit, noise control, and merge-gate safety.
Read article →
State of Behavioral Change Risk in .NET
A field report from 610 merged C# PRs across 61 repositories, with raw findings, high-confidence findings, and outlier disclosure.
Read article →
AngleSharp PR #1159 Analysis
HTML parser library pull request introducing behavioral changes.
Read article →