From 00d4ca8d912ffad87d77d11b457e98c3321a60c9 Mon Sep 17 00:00:00 2001
From: Mahdi Azarboon <21277296+azarboon@users.noreply.github.com>
Date: Tue, 11 Jun 2024 13:37:14 +0800
Subject: [PATCH] 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
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 3f13cb1..5a4fea8 100644
--- a/README.md
+++ b/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.