Let TDD drive your tests, that's fine. But then delete them. They put each class in a cage. Test against the API? Yes. Boring and limited? Absolutely. Use generators to build your cases. Give Property Testing a shot! :) and watch @jessitron - Awesome talk
https://t.co/Fp9yDfkpEj
@josejorgexl But that's the hardest part, isn't it? Putting the exact right amount of abstraction up front. When you say they should be applicable to a lot of problems - that sounds like programming with generics only? :) The essence : Writing maintainable problem solving code (?)
@vponamariov Mhm maybe tl;dr : open the bookmark, put your thoughts into a plain text file. Each day a few, you'll get through you stock pile of "do later". Plain text will be searchable for years to come :)
@oliverjumpertz As professional Software developer, we implement business cases, right ? Business cases derive from business - it's unlikely that two departments share same responsibility. Real problem seems to me: The code does not reflect the domain! DDD :)
@oliverjumpertz Classes depend. If nothing else depends on it, why sperating it ? Only reason for that would be for me the goal of have smaller functions, easier to comprehend. But then that's not SRP, is it? And .. sorry one more thread needed :D
@oliverjumpertz I am not really familiar with javascript.. what to mean with "function level"? :) And I mean, when the document needs a greeting based on country - you will either create a new function and modify the createDocument or you change the greeting function, in which might other 1/2
@oliverjumpertz I remembered! Shouts out to @monicalent for this awesome talk! I learnt a lot about architecture and it woke my interest in that topic after hearing your talk. https://t.co/mYdlNDCply at 21:10
@oliverjumpertz Cool :) i don't recall who said it, but what you think about following: never abstract, until you find yourself changing in different files the exact same code for one business request? As SRP is about business cases.