I just noticed that there are more people that have realized that OO side-effect free programming leads to more testable code, and that it is very similar to functional programming. That is pretty much exactly what I said about how unit tests make you use functional programming practices.
Today I need to write some test-cases to demonstrate how to use emock for a realistic code-base. I need to make a convincing argument that it is a Good Thing™ to make your dependencies parametric to startup code. This is because I got this remark earlier today:
noss: I mean, I don’t want to code in a way that is enforced by my testing framework, but I want to code and have the framework adapt. (that’s only possible to a degree, of course)