From acc4ac4badc1b2f8a04509c0d364492aa32b77ea Mon Sep 17 00:00:00 2001 From: Artem Zakirullin Date: Fri, 18 Oct 2024 18:18:28 +0300 Subject: [PATCH] rem author as I am not sure who is the author --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index fab7677..e015639 100644 --- a/README.md +++ b/README.md @@ -142,7 +142,6 @@ All too often, we end up creating lots of shallow modules, following some vague We make changes to our systems to satisfy our users and stakeholders. We are responsible to them. > A module should be responsible to one, and only one, user or stakeholder. -> **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. It has nothing to do with the number of things we do in our module.