2 ms·
TFA says "For example, when building SportStats v2 at the BBC we thought we needed a database for persistence. But we didn't build it in until we needed it, and
by SideburnsOfDoom 12y ago
TFA says "For example, when building SportStats v2 at the BBC we thought we needed a database for persistence. But we didn't build it in until we needed it, and we didn't mock it out either. We waited until the code told us that we now needed a database. It never did"
So they seem to be saying "if you write code upfront before you need it, you might not need it, therefor mocking is bad"
IMHO, that is not a valid conclusion to draw.
- the_af 12y agoI agree with you, that seems to be what the author is saying, and his conclusion doesn't follow. Also, I'm not sure if he really means mocking or any kind of test doubles. I thought everyone agreed that writing code upfront before you need it is always a bad idea, especially specific implementations like a database.