Update README.md

Before diving into any of the patterns, readers should be reminded of two fundamental laws in software architecture:

1.Everything is a trade-ff
2."Why is more important than the how"

So, readers face the nuances and reality of these patterns from the beginning. These two laws are coined by two thought leaders in software architecture: Mark Richards and Neal Ford. They have explained these two laws in various conference talks and books. For example, here you can read about these two laws here:

https://www.infoq.com/podcasts/software-architecture-hard-parts/


Also, here is a book for reference:
https://a.co/d/fKOodW9

Author: azarboon

README.md

@@ -8,7 +8,7 @@ or [Download as PDF/Epub](https://readthedocs.org/projects/designpatternsphp/dow
 
 This is a collection of known design patterns and some sample codes on how to implement them in PHP. Every pattern has a small list of examples.
 
-I think the problem with patterns is that often people do know them but don't know when to apply which.
+I think the problem with patterns is that often people do know them but don't know when to apply which. Remember that each pattern has its own trade-offs. And you need to pay attention more to why you're choosing a certain pattern than to how to implement it.
 
 ## Installation
 You should look at and run the tests to see what happens in the example.