On HN, it's not debatable: you should definitely do it. Everywhere I've ever worked, it's also not debatable: no time or effort should be "wasted" writing unit tests, that's what QA is for.
> no time or effort should be "wasted" writing unit tests, that's what QA is for.
This is not my experience at all, everywhere I worked unit tests are required.
I don't agree at all, writing unit tests is not a waste of time, this sentiment comes from people who don't know how to avoid brittle tests.
It's impossible for QA to test every single path in your code. Unless you wanna cover all of those in your slow end to end tests?
Oh, you're preaching to the choir here, pal. It's incredibly frustrating. I have reason to hope, though... when I first started programming in the 90's, I would fight with my co-workers about using version control (I insisted on it, they said it was a waste of time). Now, people who oppose version control are off selling life insurance or whatever happens to people who probably shouldn't be writing computer programs.
This is not my experience at all, everywhere I worked unit tests are required. I don't agree at all, writing unit tests is not a waste of time, this sentiment comes from people who don't know how to avoid brittle tests.
It's impossible for QA to test every single path in your code. Unless you wanna cover all of those in your slow end to end tests?