AjakoTaja
A look back at 'WTFs per Minute': A 2008 metric for code quality
Trending · Score 63
1 min readUpdated 1h ago
Drafted by AI, reviewed by the Ajako Taja Editorial Team · How we use AI

AI Summary

Revisiting Tom Cargill's 2008 'WTFs per minute' metric, a tongue-in-cheek measure of code quality that persists as an informal benchmark for readability in developer culture.

  • Tom Cargill coined 'WTFs per minute' as a humorous but pointed informal metric for assessing code review quality.
  • The concept gained traction in software engineering circles as an alternative to formal, often bloated, quantitative code metrics.
  • While widely cited, the metric lacks standardized application and remains entirely subjective, making it difficult to use for objective performance benchmarking.

Tom Cargill's 2008 'WTFs per minute' concept characterizes code quality by the frequency of expressions of confusion during a review. This informal standard emerged as a counter-reaction to the rigid, metric-heavy development environments of the early 2000s, where lines-of-code and complexity scores often failed to capture actual maintainability. However, the metric remains purely anecdotal, with no mechanism for scaling or consistent implementation across diverse team cultures. Whether or not it serves as a legitimate quality indicator, the persistence of the term highlights a broader industry preference for intuitive, developer-centric feedback over algorithmic management.

Get the story before everyone else.

1-minute briefings. Zero noise. Straight to your inbox.

Join our growing community of readers

Discussion

No comments yet. Be the first to start the conversation!

Leave a comment

Comments are reviewed for community standards.