From 1a98980fbf70a3da172fccb1fd193a2a9e097a76 Mon Sep 17 00:00:00 2001 From: Kamran Ahmed Date: Mon, 23 Jan 2023 03:24:56 +0400 Subject: [PATCH] Update src/roadmaps/software-design-architecture/content/100-clean-code-principles/101-be-consistent.md --- .../content/100-clean-code-principles/101-be-consistent.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/roadmaps/software-design-architecture/content/100-clean-code-principles/101-be-consistent.md b/src/roadmaps/software-design-architecture/content/100-clean-code-principles/101-be-consistent.md index 16466af23..c0449e1f5 100644 --- a/src/roadmaps/software-design-architecture/content/100-clean-code-principles/101-be-consistent.md +++ b/src/roadmaps/software-design-architecture/content/100-clean-code-principles/101-be-consistent.md @@ -1,7 +1,7 @@ # Be Consistent -Being consistent in system design architecture refers to maintaining a consistent pattern or structure in the design of a system. This can include using consistent naming conventions, data structures, and interfaces throughout the system, as well as adhering to established design principles and best practices. Consistency can help to make the system more maintainable, understandable, and extendable. +Being consistent refers to maintaining a consistent pattern. This can include using consistent naming conventions, data structures, and interfaces throughout the system, as well as adhering to established design principles and best practices. Consistency can help to make the system more maintainable, understandable, and extendable. Learn more from the following links: -- [Strongly Consistent vs Eventually Consistent for System Design](https://medium.com/double-pointer/strongly-consistent-vs-eventually-cosistent-for-system-design-interview-f67f9c1882ed) \ No newline at end of file +- [10 Tips for Writing Clean Code](https://www.pluralsight.com/blog/software-development/10-steps-to-clean-code) \ No newline at end of file