The Bell Curve of Code Review Pragmatism
Description
This meme uses the 'IQ Bell Curve' or 'Galaxy Brain' format to illustrate the evolution of a developer's mindset. It features a blue bell curve representing the distribution of intelligence or experience. At the far left (low end), a simple-minded Wojak character says, 'This code works so we're good,' representing a junior's focus on pure functionality. In the middle of the curve (average), a crying, panicked Wojak character exclaims, 'Noooo this is an antipattern, guidelines advise against it, I will create a design change proposal and follow up via a pull request shortly.' This depicts the mid-level engineer who is dogmatic about rules and processes. At the far right (high end), a stoic, hooded Wojak character simply states, 'LGTM' ('Looks Good To Me'), with a small parenthetical thought, '(I have better things to care about).' This represents the seasoned senior engineer who has the wisdom to be pragmatic, understanding that perfect is the enemy of good and that some battles aren't worth fighting. The joke is a commentary on how developers mature from a naive state, through a period of rigid adherence to theory, to a final state of experienced pragmatism
Comments
9Comment deleted
A junior dev asks if the code works. A mid-level dev asks if it follows SOLID principles. A senior dev asks if it solves the business problem and is easy to delete
Our bell-curve of code reviews: two juniors approve because it compiles, the statistically significant middle bikesheds SOLID for three days, and the staff engineer drops a Zen “LGTM” knowing the feature flag’s already set to 0% in prod anyway
The middle 68% are writing design docs for a getter method while the extremes are either shipping to prod on Friday or have already mentally checked out to work on their blockchain startup
Seniority is realizing the design change proposal will outlive the service it proposes to change
The bell curve perfectly captures the career arc: junior devs ship code that 'just works,' mid-level engineers spiral into analysis paralysis over every antipattern and RFC, and senior engineers circle back to 'LGTM' because they've learned that perfect is the enemy of shipped - though now they're wise enough to know which battles actually matter and which PRs deserve a rubber stamp at 4:59 PM on Friday
Left tail writes RFCs for a setter; right tail LGTMs refactors - meanwhile, peak just compiles
Code review bell curve: junior “it works”; mid “guidelines say it’s an antipattern, RFC inbound”; staff “LGTM - wrap it behind an interface and ship; SLOs trump purity and the rewrite isn’t funded.”
Senior review heuristic: if it’s feature‑flagged, idempotent, and easily rolled back, the opportunity cost of perfect architecture exceeds the error budget - LGTM
True Comment deleted