If I write code without tests I will end up with low quality code.
Worse - I'll discover that having written code without tests I've naturally
ended up with a codebase that resists being tested.
When this happens the codebase is not being 'malicious'.
That's just that way it is. That's exactly the way I grew it.
Testability isn't something that appears by magic.
If I want a codebase to be testable I have to write tests for it as I go along.
So that I find out just how testable it actually is and steer accordingly.
I'm 2E years old (hex). I've loved software since I was 10 (dec). I'm a self employed software consultant-trainer-programmer-etc specializing in practice, people, process, agility, test driven development, and complex-adaptive systems-thinking. I built cyber-dojo.com to promote deliberate practice for software developers. I've worked with Accenture, Aviva, Cisco, Ericsson, Friends Provident, HP, Microsoft, Opera, Ordnance Survey, RBS, Reuters, Renault F1, Schlumberger, Tandberg and many many more. If you don't like my work I won't invoice you.
I'm the ex ECMA TG2 C# convenor. I'm the current ACCU conference chairman.
I've had some C# books published. I'm married to the beautiful Natalie, and proud father of Ellie, Penny and Patrick. I love freshwater river fishing.
I live in Somerset, England. On twitter I'm @JonJagger