I've never written tests for my projects. I hate writing tests because almost certainly, as I'm creating a new software, things change. I'm focused on the changing part all the time I hate being bogged down by having to write a script that tells me everything is fine.
I agree with this. You (I) waste as much time trying to work out if the test is wrong, or the code is wrong. Fiddle until the bar goes green. Doesn't help you focus on the main problem. Show it to the users, and the requirements instantly change anyway.....
In some cases automated tests are helpful, but not everywhere.
Where do you draw the line between "creating new software" and a "large scale project"? Every large scale project starts as a small project, so at some point you must decide to start writing tests; and then you have the burden of backfilling 'em.
On a large scale project, I understand the need.