Moving on with the virtual learning series, this Thursday it is ISP.
We will start with the “Fat and polluted interface” and understand pain point. Typically any classes that have fat interface are not cohesive. In other word client is trying to serve too many client at same type.
Our demo will existing fat interface and its current client. As we understand the problem, we will then refractor it to honor ISP.
Here is the definition as taken from Wiki (for reference):
It is a software development principle used for clean development and is intended to help a developer from making his software impossible to change. If followed, the ISP will help a system stay decoupled and thus easier to refactor, change, and redeploy.