What is a good gauge for knowing when a class is poorly designed or even necessary. In other words when to write a class and when no to.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is a good gauge for knowing when a class is poorly designed or even necessary. In other words when to write a class and when no to.
SOLID might help if a class is poorly designed, but it won’t help answer a question like “Is object-oriented programming the best approach for this problem?”
People have done a lot of very good work in programming for mathematics and science before object-oriented programming came into vogue. If your problem falls into those categories, perhaps object-oriented programming isn’t for you.
Objects are state and behavior together; they tend to map onto problem domain objects one-to-one. If that’s not true for your problem, perhaps object-oriented programming isn’t for you.
If you don’t know an object-oriented language well, perhaps object-oriented programming isn’t for you.
If your organization doesn’t know and can’t support object-oriented solutions, perhaps object-oriented programming isn’t for you.