POODR Book Club Chapter 6

In this chapter, Metz progressively builds an example of inheritance with classes that share some common behavior while maintaining their own unique characteristics. Through careful handling of abstract and concrete behavior, as well as strategic implementation of template methods, refactoring with inheritance can greatly reduce the cost of change.
Below are a few questions to get our conversation started around Chapter 6. Feel free to answer any one of these and reply with a helpful comment on someone else’s post as well.

1. Can you explain in your own words why the chapter recommends to “push everything down and then pull some things up” when refactoring into an inheritance hierarchy (p.122)?
2. What guidelines might you suggest to identify when inheritance is appropriate for a particular project?
3. Any other thoughts or questions you have on this chapter?