Conventional wisdom as an anti-pattern
&#x2F;&#x2F; Tests waste a lot of time<p>Back when I was a developer, I had a manager who was super religious about unit tests (this seemed incongruous to me, I was a senior lead at the time and it was my vibe that such tests weren&#x27;t what the project really needed the most at the time)<p>The basic &quot;problem&quot; I have with tests is that - at least maybe in my experience - things tend to go wrong in cases that you <i>haven&#x27;t</i> thought about so your tests don&#x27;t cover them anyway.<p>Like, what&#x27;s the point of asserting that add(2,2) will yield 4 if you&#x27;ve already been thinking about that. And then, if you&#x27;ve already thought more complicated cases (eg negative numbers, cases that overflow) then your code already very likely handles them. And if you hadn&#x27;t thought about them, your tests won&#x27;t cover them either.<p>I get it, it&#x27;s cool to be able to run a test suite especially if I refactored something and be like &quot;yup, add(2,2) is still 4!) but not sure how much actual value vs cost&#x2F;annoyance I&#x27;ve seen from it.