But, seriously, if you find that you are creating one that looks like a simple job A large number of courses, then you may be too detailed. If your course looks messy, then you may be too rough. Please forgive me if that is an obvious statement.
I think it is A vague, no hard and fast rule case that shows us why we need human programmers. If you find yourself going too far in one direction or the other, try it out, seeking balance and refactoring . Remember: if it’s worth doing, it’s worth doing badly.
When applying the single responsibility principle and looking at the reason for the class change, how do you determine the reason for the change? Is it too detailed or not enough?
Apart from “use your judgment” based on your experience, I don’t know a good answer to this question. That’s right, get help, I guess What are you doing here 😉
But, seriously, if you find that you are creating a large number of courses that look like a simple job, then you may be too detailed. If your course looks messy, then you may be too rough. Please forgive me if that is an obvious statement.
I think this is a vague, no hard and fast rule case, Show us why we need human programmers. If you find yourself going too far in one direction or the other, try it out, seek balance and refactoring. Remember: if it’s worth doing, it’s worth doing badly.