Code Smells Are Not Subjective: How to Make Your Review Objective
A field report on making code review objective using static analysis metrics, small PRs, and a quality gate.
Code Smells
Code Smells
7 articles in this category
Code Smells
Code Smells Aren't Subjective: How to Make Your Review Objective
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...
Code Smells
Stop Tolerating Code Smells: A Blunt Code Review Walkthrough
You think code smells are just a nuisance? Wrong. This practical guide shows you how to spot and fix them in review, with a concrete example and hard ...
Code Smells
Code Smells Are the Bugs You Haven't Found Yet: A Field Report
Chasing bugs is fine, but code smells are the real threat. A field report on how hunting smells first—not just waiting for bugs—keeps your codebase he...
Code Smells
Code smells hide the bugs that will bite you later — hunt them first
Code smells aren't just style. They're early warnings for bugs that will surface later. If your review only checks for functional bugs, you're missing...
Code Smells
Code Smells Are Not Bugs: Stop Treating Them Like They Are
You've been told to fix every code smell your linter flags. That's a trap. Here's how to tell real problems from noise, and why reviewing for maintain...
Code Smells
How Small Should Your Pull Request Be? The 100-Line Test
Google's data shows median changes are 24 lines. If your PR is over 400 lines, you're doing it wrong. Here's how to split.