This is review of the 10th chapter from the book-”Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin
In this chapter- we now move on to bigger blocks- Classes
Robert goes through the design principles behind classes. Mostly the SOLID principles he advocates in many of his works.
Single Responsibility Principle
Open Closed Principle
Greater cohesion between classes
Dependency Inversion Principle.
The most important message was- be ready for change. Software is ever evolving. And so do all the blocks of your software
If you see a class- loosing cohesion- maybe it’s the time to break it into smaller components.
You observe a class is getting modified for newer features again and again- maybe you need to redesign it to open it for extensions.
You don’t have to get the whole picture right – from the beginning. The important part is to understand when is tge time to refactor your units of software
By programming against abstractions- you avoid a close binding with implementations- making it easier for newer changes to be brought in
For review of other chapters- please see this post.
Pingback: Book Review: Clean Code: A Handbook of Agile Software Craftsmanship | Technology Cafe