Interfaces, decoupling and change resilience

Code bellow is part of me explaining my ongoing software architecture advice: try to minimize the (class) inheritance.

As a general rule, I solve the required behavior first, data second.

TODO: UML diagram is in order here. It is coming.

 

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.