Notes on shipping better code.
Engineering essays and product notes from the team building Impact.
What Is Blast Radius in Software Development?
Read more →What code churn actually tells you about bug risk
Files that change constantly are where bugs live. Here's why churn is one of the most predictive — and most ignored — signals in your codebase.
Read more →Designing a quality gate your team won't route around
A gate that blocks every merge gets disabled by Friday. Here's how to set thresholds that actually stick.
Read more →Reading a dependency graph: finding the modules that will hurt you
A dependency graph isn't just a pretty picture. Here's how to read one to find the parts of your architecture most likely to cause pain.
Read more →How we score maintainability (SQALE, explained)
An A–F grade is only useful if you trust how it's calculated. Here's the methodology behind the maintainability score.
Read more →Why we built Impact Code Analysis
Good code intelligence existed — it was just fragmented across five tools and priced for enterprises. So we built one platform that does all of it.
Read more →Self-hosting code analysis without the headache
For teams that can't send source code to a SaaS, self-hosting shouldn't mean a week of DevOps. Here's how we made it turnkey.
Read more →