When argumenting with other coders I lean on the architect side: do the things right, even if it means thinking and forecasting for two hours more. And it do no

When argumenting with other coders I lean on the architect side: do the things right, even if it means thinking and forecasting for two hours more. And it do not mean rigidity: sane architectures are those that allow a lot of flexibility, as much as you can run one any kind of road under any weather with a good 4x4, while a crappy car will break as soon as you leave the highway. But I also advocate strongly for unit testing. Maybe it is because I write in Python for web and use unit test to run and prove the lines of code I write (I really hate going to the browser and re-clicking on the knob). But still, I think you are a bit wrongish in your anti-TDD view. Say, check the first programming classes by Norvig in udacity. He should probably not be classified in the Cowboys, but his first step is writing the testing code.