Move DRY down a bit

Author: webpro

README.md

@@ -22,10 +22,10 @@ have any feedback or suggestions for improvement!
 - [YAGNI](#yagni)
 - [Do The Simplest Thing That Could Possibly Work](#do-the-simplest-thing-that-could-possibly-work)
 - [Separation of Concerns](#separation-of-concerns)
-- [Keep things DRY](#keep-things-dry)
 - [Code For The Maintainer](#code-for-the-maintainer)
 - [Avoid Premature Optimization](#avoid-premature-optimization)
-- [Boy-Scout Rule](#boy-scout-rule)
+- [Keep things DRY](#keep-things-dry)
+- [Boy Scout Rule](#boy-scout-rule)
 
 ### Relationships between modules, classes, components, entities
 
@@ -141,51 +141,6 @@ Resources
 
 - [Separation of Concerns (wikipedia.org)](https://en.wikipedia.org/wiki/Separation_of_concerns)
 
-## Keep things DRY
-
-**Don't Repeat Yourself**: Every piece of knowledge must have a single,
-unambiguous, authoritative representation within a system.
-
-Each significant piece of functionality in a program should be implemented in
-just one place in the source code. Where similar functions are carried out by
-distinct pieces of code, it is generally beneficial to combine them into one by
-abstracting out the varying parts.
-
-Why
-
-- Duplication (inadvertent or purposeful duplication) can lead to maintenance
-  nightmares, poor factoring, and logical contradictions.
-- A modification of any single element of a system does not require a change in
-  other logically unrelated elements.
-- Additionally, elements that are logically related all change predictably and
-  uniformly, and are thus kept in sync.
-
-How
-
-- Put business rules, long expressions, if statements, math formulas, metadata,
-  etc. in only one place.
-- Identify the single, definitive source of every piece of knowledge used in
-  your system, and then use that source to generate applicable instances of that
-  knowledge (code, documentation, tests, etc).
-- Apply the
-  [Rule of three](<https://en.wikipedia.org/wiki/Rule_of_three_(computer_programming)>).
-
-Resources
-
-- [Dont Repeat Yourself (wiki.c2.com)](http://wiki.c2.com/?DontRepeatYourself)
-- [Don't repeat yourself (wikipedia.org)](https://en.wikipedia.org/wiki/Don't_repeat_yourself)
-- [DRY Principle: Its Benefit and Cost with Examples (thevaluable.dev)](https://thevaluable.dev/dry-principle-cost-benefit-example/)
-
-Related
-
-- [Abstraction principle (wikipedia.org)](<https://en.wikipedia.org/wiki/Abstraction_principle_(computer_programming)>)
-- [Once And Only Once (wiki.c2.com)](http://wiki.c2.com/?OnceAndOnlyOnce) is a
-  subset of DRY (also referred to as the goal of refactoring).
-- [Single Source of Truth (wikipedia.org)](https://en.wikipedia.org/wiki/Single_Source_of_Truth)
-- A violation of DRY is [WET](http://thedailywtf.com/articles/The-WET-Cart)
-  (Write Everything Twice)
-- [Be careful with the code metric "duplicated lines" (rachelcarmena.github.io)](https://rachelcarmena.github.io/2018/02/27/duplication-you-are-welcome.html)
-
 ## Code For The Maintainer
 
 Why
@@ -237,6 +192,51 @@ Resources
 - [Program optimization (wikipedia.org)](https://en.wikipedia.org/wiki/Program_optimization)
 - [Premature Optimization (wiki.c2.com)](http://wiki.c2.com/?PrematureOptimization)
 
+## Keep things DRY
+
+**Don't Repeat Yourself**: Every piece of knowledge must have a single,
+unambiguous, authoritative representation within a system.
+
+Each significant piece of functionality in a program should be implemented in
+just one place in the source code. Where similar functions are carried out by
+distinct pieces of code, it is generally beneficial to combine them into one by
+abstracting out the varying parts.
+
+Why
+
+- Duplication (inadvertent or purposeful duplication) can lead to maintenance
+  nightmares, poor factoring, and logical contradictions.
+- A modification of any single element of a system does not require a change in
+  other logically unrelated elements.
+- Additionally, elements that are logically related all change predictably and
+  uniformly, and are thus kept in sync.
+
+How
+
+- Put business rules, long expressions, if statements, math formulas, metadata,
+  etc. in only one place.
+- Identify the single, definitive source of every piece of knowledge used in
+  your system, and then use that source to generate applicable instances of that
+  knowledge (code, documentation, tests, etc).
+- Apply the
+  [Rule of three](<https://en.wikipedia.org/wiki/Rule_of_three_(computer_programming)>).
+
+Resources
+
+- [Dont Repeat Yourself (wiki.c2.com)](http://wiki.c2.com/?DontRepeatYourself)
+- [Don't repeat yourself (wikipedia.org)](https://en.wikipedia.org/wiki/Don't_repeat_yourself)
+- [DRY Principle: Its Benefit and Cost with Examples (thevaluable.dev)](https://thevaluable.dev/dry-principle-cost-benefit-example/)
+
+Related
+
+- [Abstraction principle (wikipedia.org)](<https://en.wikipedia.org/wiki/Abstraction_principle_(computer_programming)>)
+- [Once And Only Once (wiki.c2.com)](http://wiki.c2.com/?OnceAndOnlyOnce) is a
+  subset of DRY (also referred to as the goal of refactoring).
+- [Single Source of Truth (wikipedia.org)](https://en.wikipedia.org/wiki/Single_Source_of_Truth)
+- A violation of DRY is [WET](http://thedailywtf.com/articles/The-WET-Cart)
+  (Write Everything Twice)
+- [Be careful with the code metric "duplicated lines" (rachelcarmena.github.io)](https://rachelcarmena.github.io/2018/02/27/duplication-you-are-welcome.html)
+
 ## Boy Scout Rule
 
 The Boy Scouts of America have a simple rule that we can apply to our