How and why to write testable code

In my personal experiance, highly testable code often equals good code. My deffinition of good code is that it should be loosly coupled layers, follow basic object oriented principals, small methods, good readability and it shouldn´t have much code duplication. I find, that if you think about testing or use TDD while writing your code, you will automaticly follow those "rules" pretty good.