add new chapter about SRP and shallow modules

README.md

@@ -159,7 +159,7 @@ We make changes to our systems to satisfy our stackeholders and users. We are re
 > A module should be responsible to one, and only one, user or stackeholder.  
 > **Uncle Bob**
 
-This is what this Single Responsibility Principle is all about. Simply put, if we introduce a bug in one place, and then two different business people come to complain, we've violated the principle.  
+This is what this Single Responsibility Principle is all about. Simply put, if we introduce a bug in one place, and then two different business people come to complain, we've violated the principle. It has nothing to do with the number of things we do in our module.    
 
 But even now, this interpretation can do more harm than good. This rule can be understood in as many different ways as there are people. Looking back at how much cognitive load a decision induces is a more clearer way.