Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Using one anecdotal experience as proof is not the exact opposite of a strawman.

A strawman argument is an argument no one is actually making, but one that's easy to debate against (to "knock down"). So even "one anecdotal experience" implies there is someone making that argument and it's not a strawman. Moreover, as I said above, it's not a single anecdote, but experience with many, many companies, including ones I worked for directly, those that are the clients of my company (http://atomic-squirrel.net/), and the many companies I interviewed while writing my book. Of course, the plural of anecdote is not "data", but I'm pretty sure that you don't need statistically significant data sets to show your argument isn't a strawman.

> These numbers don't line up with any experience I've ever had. In my opinion the value of testing should stand on its own without having to exaggerate.

If anything, it's not an exaggeration, but an underestimate. I can't count how many hours I've lost to debugging that could've easily been saved by a handful of automated tests. But perhaps you're a better programmer than I am, and I envy that your code works perfectly regardless of whether you write tests or not.



> I can't count how many hours I've lost to debugging that could've easily been saved by a handful of automated tests.

Undoubtedly, but be careful you're not suffering from confirmation bias, are you properly accounting for all the tests you wrote that never detected an issue, where they didn't save tons of time in a major refactor (because it never happened)?

> But perhaps you're a better programmer than I am, and I envy that your code works perfectly regardless of whether you write tests or not.

http://blog.dilbert.com/post/141657128476/the-sarcasm-tell-w...




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: