“Unit tests are a waste of time. They just double the work. Nobody reads them anyway.”
These kinds of statements pop up in tech all the time. They’re easy to dismiss as ignorance or laziness, but that’s rarely the full story. Hot takes like these often come from real frustrations, particularly with how the work is being done rather than what the work is meant to accomplish.
If you’re leading a team, you can’t afford to treat these comments as noise. They’re signals. Rough, emotionally charged, sometimes exaggerated signals, but signals nonetheless.
Why You Shouldn’t Dismiss the Take
When someone says “unit tests are a waste of time,” they’re not actually debating the abstract value of testing. They’re reacting to a specific experience: tests that break for no reason, test suites that don’t catch bugs, test code that’s harder to read than the production code, or processes that prioritize coverage metrics over quality.
If you respond by launching into a lecture about testing best practices, you’ve already lost the thread. You’ve turned a chance to learn into a contest of who’s right.
Instead, treat the hot take like a probe. It’s poking at something real, even if the message is messy.
A Framework for Truth Extraction
Here is a simple way to unpack what’s going on behind the scenes when someone makes a sweeping, “bad” statement:
-
Zoom out on the context Ask: What kind of environment would make that take feel valid? Maybe the team inherited brittle legacy tests. Maybe they’re under constant time pressure. Context reframes the comment.
-
Unpack the pain Most bad takes stem from friction. Is it that tests are too hard to maintain? That they don’t give useful feedback? That they slow down iteration without adding value? You’re not looking for the perfect answer—you’re listening for pain points.
-
Find the misapplied truth “Unit tests are a waste of time” might reflect a team that’s forced to write tests for everything, regardless of usefulness. The grain of truth is that not all code benefits from unit tests. The problem isn’t with testing itself, it’s how rigidly and indiscriminately testing is enforced.
-
Separate emotion from insight A frustrated tone doesn’t invalidate the experience. You can acknowledge what someone’s gone through without agreeing with their conclusion. Be curious, not combative.
-
Offer a better frame Once you’ve clarified the issue, reframe it. Instead of “unit tests are a waste of time,” try: “We need to be more thoughtful about where tests add the most value. Let’s make sure they help us move faster, not slower.”
Why This Matters for Leaders
This isn’t about coddling people. It’s about being effective.
Engineers, peers, and execs all throw out strong opinions, especially under pressure. If you dismiss a frustrated developer, ignore a skeptical stakeholder, or shut down a critical voice on your team, you lose credibility. Worse, you lose the chance to actually fix the thing they’re reacting to.
When you find common ground inside a bad take, you defuse tension. You help people feel heard without letting the conversation stall out in negativity. That’s how you build trust. That’s how you influence the direction of the work.
Hot takes might be poorly worded, but they’re rarely random. They come from lived experience, often rooted in frustrations with tools, practices, or processes that fail to deliver on their promise.
As a leader, your job isn’t to shut those takes down. It’s to decode them. Because buried inside even the most cynical comment is usually a useful clue about how people work, what they need, and what’s not working yet.
Look for the grain of truth. That’s where the real leverage is.