Should Code Smells Block a Pull Request?
Code smells rarely break production, but they can predict future pain. Here's a practical take on when to block a merge—and when to let it go.
15 articles in this category
Code smells rarely break production, but they can predict future pain. Here's a practical take on when to block a merge—and when to let it go.
Static analysis and human review catch different smells. We compare SonarQube, Semgrep, and human review on three criteria and declare a winner for ea...
Stop burning out your reviewers on complexity thresholds and duplication. Let tools flag the boring stuff. Save humans for the weird, judgment-heavy p...
I pit SonarQube, Semgrep, and human review against each other to help you decide how to catch code smells without wasting your team's time.
Chasing code smells with static analysis alone misses the real fix: process. Google's data shows review speed and small changes matter most.
Stop ignoring code smells in review. Here's my hands-on guide to catching them early, fixing them fast, and keeping your codebase healthy—without bike...
I argue that chasing code smells hurts code review. The real target should be cognitive complexity and maintainability, not isolated smells.
Code review isn't about catching bugs—it's about stopping code smells. Here's how to shift your focus and improve code health.
I argue that obsessing over code smells during review is a trap. The real goal is code health, not perfection. Learn why you should approve that 'smel...
We obsess over code smells in the diff, but the biggest smell is a review process that's slow, unfocused, and defensive. Here's how to fix yours.
Static analysis tools catch mechanical issues, but human review finds design problems. Here's how to balance both for better code health.
Code smells aren't bugs. They're signals. Here's how to tell them apart, why most static analyzers miss the point, and why your review should focus on...
Code smells aren't the real problem. You're wasting review time on nits while the big picture—design, clarity, and over-engineering—goes unchecked. He...
A field report on making code review objective using static analysis metrics, small PRs, and a quality gate.
Many devs think code smells are just style preferences. Wrong. They're measurable, and your review should measure them. Here's how to use static analy...