I totally agree with you. I'm all for TDD. I haven't made my intentions clear in this particular article as when I wrote it, my main idea was to give an alternative opinion for an interim way of doing this with the ultimate aim of driving towards a TDD philosophy.

By no means I am suggesting, encouraging, or promoting that non TDD is a best-practice within this industry & I totally acknowledged that my language used in this particular article might lead the reader into thinking that.

It just, that over the years I have seen on numerous occasions on many projects that don't practice TDD and such that not even a single tests are written, let alone written it afterwards, hence my article in the first place.