Unit Testing Is Overrated
I can&#x27;t believe I&#x27;m wasting my time on another testing debate.<p>Speaking as a formerly young and arrogant programmer (now I&#x27;m simply an arrogant programmer), there&#x27;s a certain progression I went through upon joining the workforce that I think is common among young, arrogant programmers:<p>1. Tests waste time. I know how to write code that works. Why would I compromise the design of my program for tests? Here, let me explain to you all the reasons why testing is stupid.<p>2. Get burned by not having tests. I&#x27;ve built a really complex system that breaks every time I try to update it. I can&#x27;t bring on help because anyone who doesn&#x27;t know this code intimately is 10x more likely to break it. I limp to the end of this project and practically burn out.<p>3. Go overboard on testing. It&#x27;s the best thing since sliced bread. I&#x27;m never going to get burned again. My code works all the time now. TDD has changed my life. Here, let me explain to you all the reasons why you need to test religiously.<p>4. Programming is pedantic and no fun anymore. Simple toy projects and prototypes take forever now because I spend half of my time writing tests. Maybe I&#x27;ll go into management?<p>5. You know what? There are some times when testing is good and some times where testing is more effort than it&#x27;s worth. There&#x27;s no hard-set rule for all projects and situations. I&#x27;ll test where and when it makes the most sense and set expectations appropriately so I don&#x27;t get burned like I did in the past.