[bethly]

I've had business people tell me I should stop writing tests so I could go faster, even when I'm producing significantly more features than the developers around me who don't write tests. Once you get good at testing, writing code with tests is faster than writing code without tests: the challenge is the four to six year learning curve to get there.

I think we just need to stop telling people that code without tests is an option. It is an integral part of being a software developer, not a nice-to-have afterthought.

[D-Coder]

"I've had business people tell me I should stop writing tests so I could go faster"

Maybe tell them that double-entry bookkeeping doubles their workload and they could go faster with single-entry bookkeeping.

[sjellis]

"Once you get good at testing, writing code with tests is faster than writing code without tests: the challenge is the four to six year learning curve to get there."

This is the problem. Testing is not easy, and many developers simply aren't very proficient at it. Worse, we often don't recognise that it is a separate but important skill.