[shaunw321]

Lots of great examples and philosophies here.

I think, for me, I am often on two sides of the situation.

1. I'm moving fast and writing code to get things done for the customer and the product.

2. I have enough time to slow down and write or refactor "testable" code.

Often 1 results in untestable code. Often 2 results in a refactor or most likely a rewrite to create testable code.

This is an important difference. Optimizing to write code just because you think is clean (in the sense of shorter, reusable code) is often confusing to most. This also leads to pull requests that grow large and are hard or time consuming for others to review.