From 9b9ffe8bfaf1634e617bab2c42b53d067a261f01 Mon Sep 17 00:00:00 2001 From: Kamran Ahmed Date: Mon, 23 Jan 2023 03:25:30 +0400 Subject: [PATCH] Update src/roadmaps/software-design-architecture/content/100-clean-code-principles/104-keep-it-small.md --- .../content/100-clean-code-principles/104-keep-it-small.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/roadmaps/software-design-architecture/content/100-clean-code-principles/104-keep-it-small.md b/src/roadmaps/software-design-architecture/content/100-clean-code-principles/104-keep-it-small.md index 89f00e35b..d2394f3a5 100644 --- a/src/roadmaps/software-design-architecture/content/100-clean-code-principles/104-keep-it-small.md +++ b/src/roadmaps/software-design-architecture/content/100-clean-code-principles/104-keep-it-small.md @@ -1,3 +1,3 @@ # Keep it Small -Keep it small in system design architecture refers to the practice of designing and implementing small, focused components that serve a specific purpose, rather than large, monolithic components that try to do everything. This can help to improve the maintainability and scalability of the system by making it easier to understand, test, and modify individual components. \ No newline at end of file +You should design and implement small, focused components that serve a specific purpose, rather than large, monolithic components that try to do everything. This can help to improve the maintainability and scalability of the system by making it easier to understand, test, and modify individual components. \ No newline at end of file