fair enough. Do you think TDD and OOP are mutually exclusive practices?

TDD as I practice it does, but I think OOP as it's traditionally taught encourages developers to tangle mutable application state and behavior, which leads to all sorts of problems. The more I practice, the more I learn that life is better when I separate whatever holds the state from whatever has the behavior

> life is better when I separate whatever holds the state from whatever has the behavior

If you are not doing what is traditionally taught as OO, and you are doing something better why not say that?

I wonder why you don't say: "OO is an inferior design because it tangles mutable state with behavior"

"Not OO" should not be pejorative. OO is definitely sometimes wrong.