"Tests Are a Waste of Time"

This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).

A rebuttal to the common belief that TDD and writing tests first is a waste of time. The argument is structured in three parts: (1) professional software development is fundamentally about making guesses and verifying them through feedback loops, making tests essential; (2) writing tests first requires a testable architecture (hexagonal/clean/ports-and-adapters), which is hard to retrofit later; and (3) testing is genuinely difficult to learn but mastering it unlocks better design skills, scalable code, and career value. The post acknowledges that TDD isn't always strategic — early-stage products with no customers should focus on validating theoretical value before investing in test infrastructure.

11m read timeFrom khalilstemmler.com
Post cover image
Table of contents
1. The Entire Purpose of Professional Software Development is to GuessWhat is Value Anyway?From Pain → Benefit = ValueFrom Benefit → BenefitNegative ValueThe Guess (it's Theoretical & Physical)Strategic, Pragmatic Guessing2. To write the tests first, you need a testable architecture3. Testing Requires a High Level of Mastery (But It's The Key)