I agree. When adding tests to legacy code, I typically want more testing feedback at first, then design feedback second, hence this article: with legacy code I want to avoid too much design feedback early on, because I already know that the design needs a lot of work. At that stage, the details distract me more than they help me.
More to the point, though, I got tired of people saying that JMock was better than Mockito, or the reverse, or that spies are better than mocks, or the reverse. They're all the same, so teach each eir own. In this article I tried to describe "my own". :)