http://ravimohan.blogspot.com/2007/04/learning-from-sudoku-s...
And yet, among the most agreed ideas you can ever make in popular programming circles is that you are fond of TDD...
Unit test driven development only really works on "algorithmic" style code. Stuff that's mostly linking disparate systems together - if you try writing unit tests for it you'll end up with a mess of mocks that aren't actually testing if your code works.
I'm pretty sure, that the case study of such project will take up the whole book, not just 3 blog posts ;)
Because sum method was used to quickly explain Specific/Generic rule on the simplest example. Then it follows through with real-ish (a bit modified) business case, that has gotten me stuck in the past.
I know that readers on the internet have limited attention span, so I shouldn't have put a sum method example at the beginning, rather I should have started with the main case study and made a detour before applying this rule to the sum example.
Thanks for the feedback again, next time I will try to not make this mistake.
My complaint is akin to the modern complaints on the gang of 4 patterns. Individually they make compelling arguments and if you follow the discussion, it is appealing.
And I don't want to throw out the baby, so to speak. I think all of these make fine guidelines. We are just an industry that seems hellbent on finding prescriptive directions where it is becoming apparent none exist.