Quotes About Subclass

This leaves a big question unanswered. Is it ever appropriate to store an optional in an instance field? Often it's a "bad smell": it suggests that perhaps you should have a subclass containing the optional fields. But sometimes it may be justified.

In case you haven't noticed, they're moving a lot faster. I don't know about the laws of physics on your planet, but where I come from an object moving at subclass speed can't catch up to one running at starclass. But if you know something about turbines, thrusters and engines, quantum or classical physics that I've somehow missed, then please enlighten me. - Caillen Dagan to Desideria Denarii

inheritance is a powerful tool for reducing complexity because a programmer can focus on the generic attributes of an object without worrying about the details. If a programmer must be constantly thinking about semantic differences in subclass implementations, then inheritance is increasing complexity rather than reducing it.

For a subclass outside the package, the protected member can be accessed only through inheritance.

Unlike the names at the roots of hierarchies, subclass names aren't used nearly as often in conversation, so they can be expressive at the cost of being concise.

Parallel inheritance hierarchies is really a special case of shotgun surgery. In this case, every time you make a subclass of one class, you also have to make a subclass of another.