I just read the article, I agree with pretty much everything in there. Imo TDD (not really mentioned here but in the other article in the beginning) is still a good idea because it forces you to think about your design before getting bogged down into implementation details.<p>What often misses from such articles though is an example of how to get there. Nobody sets out to write bad code or brittle tests. So following along a codebase that used to suck and is slowly getting better would be great! Though I understand it's a much more involved exercise, I'm not holding it against the author.