The Universal Dislike of Test-Driven Development Across the Intelligence Spectrum
Description
This image uses the IQ Bell Curve meme format, also known as the Galaxy Brain meme, to comment on developer attitudes towards Test-Driven Development (TDD). The meme displays a bell curve representing the distribution of IQ scores. On the far left, a low-IQ Wojak character says, 'I HATE TEST-DRIVEN DEVELOPMENT.' In the center, representing the average majority, a crying and frustrated Wojak also says, 'I HATE TEST-DRIVEN DEVELOPMENT.' On the far right, a serene, enlightened Wojak character completes the pattern, stating, 'I HATE TEST-DRIVEN DEVELOPMENT.' The humor lies in the implication that while developers across all experience levels may dislike TDD, their reasons are vastly different. Beginners may find it difficult and counterintuitive, those with average experience might see it as a rigid, time-consuming dogma, while seasoned experts often dislike it for its limitations, recognizing situations where it's an inefficient or inappropriate tool compared to other well-architected testing strategies
Comments
23Comment deleted
Juniors hate TDD because writing tests first is hard. Mid-levels hate TDD because their manager read a book about it. Seniors hate TDD because they've learned that shipping robust features is more about thoughtful design than religious adherence to any single methodology
TDD is that rare discipline everyone hates for different reasons: the junior because the red bar feels like failure, the mid-level because mocking Kafka is dental surgery with reflection, and the architect because 3,000 Selenium tests turned the CI pipeline into a daily archaeological dig
After 20 years in the industry, I've realized TDD is like microservices architecture - everyone pretends it's working great in production while secretly maintaining a monolithic test suite that takes 45 minutes to run and breaks whenever someone looks at it sideways
The real genius move is realizing that both the junior who's never written a test and the architect who's seen TDD cargo-culted into oblivion arrive at the same conclusion - just with vastly different scars. The middle of the curve is still arguing about 100% coverage while the extremes have moved on to debating whether the real test was the friends we made along the way
TDD hate: the only normally distributed metric with 99.7% coverage across all devs, unlike any actual test suite
TDD: juniors hate the overhead, seniors hate the ossification - give it a few sprints and the test suite becomes the real legacy system
Senior translation of 'I hate TDD': not anti-tests - anti brittle mock pyramids that fossilize architecture and turn refactors into multi-sprint programs
lol Comment deleted
Everyone says you have to do TDD but nobody really does it... or likes it. Comment deleted
Depends on the target lang and stack - there's simply not enough org maturity and personal responsibility to implement a feasible and viable custom instrumentation. People are too lazy to do that and management is too negligent to admit that it's even a problem in the first place... until it blows. Comment deleted
Junior: open PR with test coverage 0% Me, a senior: Comment deleted
In my previous company I wasn't even being able to create PR without at least 50% test coverage, freaking SonarCloud rejected it Comment deleted
I don't hate TDD... and been in business for about 15 years. Comment deleted
TDD is idiotic. write Ada/spark. Comment deleted
Beware of bugs in above code. I've only proven it correct, not actually tested it. Comment deleted
Guess who hates TDD? Whose never actually did it Comment deleted
Means everyone Comment deleted
Almost, unfortunately Comment deleted
please ? Comment deleted
If you don't like my release you fucking go out with me one on one, not in the fat fucking bugs Comment deleted
1v1 me instead of debugging shit in jira Comment deleted
The way I interpret it is: #1 hates it and hence doesn't do it #2 hates it because he is forced by management to do it #3 understands that programming is hell, TDD saves time and hence uses it, but it's still painful Comment deleted
sounds correct, I agree Comment deleted