However, now you've mixed all concerns into one big Uploader and coupled them together. This means if one concern changes you need to check all of them again. While I get the point I think this post might be misleading :) I've recently blogged about this topic. WDYT? philgiese.com/post/what-is-cohesio...
I don't understand what do you mean by mixed all concern into one big Uploader. IMO, the Uploader classes are responsible for uploading to corresponding file storage and Uploader, as a static class, responsible for selecting appropriate uploader implementation. So I don't see how it is mixed together.
However, now you've mixed all concerns into one big
Uploaderand coupled them together. This means if one concern changes you need to check all of them again. While I get the point I think this post might be misleading :) I've recently blogged about this topic. WDYT? philgiese.com/post/what-is-cohesio...I don't understand what do you mean by mixed all concern into one big Uploader. IMO, the Uploader classes are responsible for uploading to corresponding file storage and Uploader, as a static class, responsible for selecting appropriate uploader implementation. So I don't see how it is mixed together.
Can you clarify it a little bit more?
I have to apologize. I must have misread something. My comment really doesn't make much sense if I read your article again. Excuse my mumbling :D