2 ms·
" have seen the "old" way do nothing but fail and the "new" way do nothing but succeed." When I look at TDD I see a lot of success but also a lot of fail once
by maxxxxx 9y ago
" have seen the "old" way do nothing but fail and the "new" way do nothing but succeed."
When I look at TDD I see a lot of success but also a lot of fail once people start pushing it too far. To me a fail is when the mock becomes more complex than the real system or a system can't be refactored because the refactoring of the tests takes too long or the tests are just so complex nobody wants to touch them.
This reminds me a little of the situation with OOP. It solved a lot of real problems but then people said "only objects" and you ended up with stuff like replacing a simple switch statement and 100 easy to read lines of code with command patterns that had the implementation spread out over 10 different files.
- sqeaky 9y agoI think you are totally correct both in your view that some take goods things too far and that this isn't the first time this pattern has been repeated. I wonder what things I am expounding now that I will pull back on in the future?