7 posts
Most CI pipelines catch syntax errors and logic bugs. They miss the API contract breaks that actually take down production. Here's how to fix that.
Every API break that made it to production on my team passed CI. All of them. The unit tests were green. The integration suite passed. The deploy went out, and…
How to run formal static analysis in your CI pipeline using Infer, with working configs and realistic trade-offs.
Abstract interpretation is the kind of term that makes engineers close the tab. It sounds like something you need a semester of lattice theory to understand.…
Literate programming promises a single source of truth, but manual weave and tangle steps break the CI/CD pipeline.
If your build pipeline cannot run without you opening a terminal and typing , you do not have a literate program. You have a diary with a compiler attached.…
Most teams document architecture rules in wikis. Here's how to write them as executable tests that fail CI when your dependency graph drifts.
Your test suite verifies that returns 42 when given the right input. It does not verify that is allowed to import . The compiler is happy with both. Your unit…
Clean architecture diagrams look great on a whiteboard.
Someone on your team just imported into . The PR compiles. The tests pass. The code review is three hundred lines long, and nobody notices. Three months later,…
Most teams don't run full mutation testing suites on every commit.
If your mutation testing suite takes four hours to run, congratulations. You've proven what everyone already suspected: your test suite has gaps. You are not…
Human review is inconsistent. AI review is worse. The only scalable defense for AI-generated codebases is deterministic enforcement: rules that fail the build, not suggestions that get ignored.
The standard advice for AI-generated code is "review it carefully." That advice is correct and useless at scale. A developer reviewing AI output catches…