> Write it. Run it. It either does what it's supposed to or not. If it doesn't, find out why and fix it
That's called functional testing and that's actually testing. You are one step removed from actually formalising what you do and getting non regression testing for free. At that point, I think you are either arguing fot the sake of it and do actually realise that testing is important or somehow confuse testing with unit testing which is only a narrow subset of it.
Congratulations. I already told you I test my programs. The discussion is about expending brain power and time writing hundreds of lines of code to test the intended user-facing code, which, in my opinion, is just dumber than a bag of hammers.
Users are not guinea pigs. They deserve better.
> Write it. Run it. It either does what it's supposed to or not. If it doesn't, find out why and fix it
That's called functional testing and that's actually testing. You are one step removed from actually formalising what you do and getting non regression testing for free. At that point, I think you are either arguing fot the sake of it and do actually realise that testing is important or somehow confuse testing with unit testing which is only a narrow subset of it.