From 4fb99bef72b8a992b33246e3402c0546a68b3981 Mon Sep 17 00:00:00 2001
From: Kyle Thorpe <kjthorpe18@gmail.com>
Date: Fri, 21 Jan 2022 00:20:16 -0500
Subject: [PATCH] DRY description and resources (#1020)

* DRY description and resources

Add a description and resources for DRY software development/design principle

* Minor space change

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>
---
 .../114-design-and-development-principles/106-dry.md      | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/content/roadmaps/101-backend/content/114-design-and-development-principles/106-dry.md b/content/roadmaps/101-backend/content/114-design-and-development-principles/106-dry.md
index 378c54dd5..5ca661937 100644
--- a/content/roadmaps/101-backend/content/114-design-and-development-principles/106-dry.md
+++ b/content/roadmaps/101-backend/content/114-design-and-development-principles/106-dry.md
@@ -1 +1,7 @@
-# Dry
\ No newline at end of file
+# DRY
+
+Don't Repeat Yourself (DRY) is a software design principle which encourages developers to not repeat software patterns or code. DRY encourages code reusability, often in the form of methods, functions, or subroutines. When DRY is implemented successfully, developers are able to make one change to update many related elements while avoiding making changes to unrelated elements.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://dzone.com/articles/software-design-principles-dry-and-kiss'>Software Design Principles DRY and KISS</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1001745#s5'>Best Practices for Scientific Computing</BadgeLink>