Poor class design IS a property of OOP. All of these logical errors that are easy to commit are terrible because they are usually runtime bugs, not compile tim

Poor class design IS a property of OOP. All of these logical errors that are easy to commit are terrible because they are usually runtime bugs, not compile time. As I think of it, I think a neat feature of OOP would be conditional methods that are only callable under specific circumstances. For example, the “Customer.SendPasswordResetEmail()” method couldn’t be called (or didn’t even exist) until I verify that the “Customer.IsEmailVerified” property is true. Being able to add these type of annotations to methods for expected object state would help catch some logic bugs at compile time.