Editing

webpro · webpro · commit bf36458744c5 · 2016-01-25T21:30:38.000+01:00
diff --git a/README.md b/README.md
@@ -14,7 +14,7 @@ The list was inspired by [The Principles of Good Programming](http://www.artima.
 * [Keep Things DRY](#keep-things-dry)
 * [Code For The Maintainer](#code-for-the-maintainer)
 * [Avoid Premature Optimization](#avoid-premature-optimization)
-* [Boyscout Rule](#boyscout-rule)
+* [Boy-Scout Rule](#boy-scout-rule)
 
 ### Inter-Module/Class
 
@@ -354,20 +354,19 @@ Resources
 
 * [Interface segregation principle](https://en.wikipedia.org/wiki/Interface_segregation_principle)
 
-## Boyscout Rule
+## Boy-Scout Rule
 
-The boyscout rule states that we should always leave the code cleaner than we found it.
+The Boy Scouts of America have a simple rule that we can apply to our profession: "Leave the campground cleaner than you found it". The boy-scout rule states that we should always leave the code cleaner than we found it.
 
 Why
 
-* When making changes to an existing codebase the code quality tends to degrade accumulating technical debt. Following the boyscout rule, we should mind the quality with each commit. Technical debt is resisted by continuous refactoring, no matter how small.
+* When making changes to an existing codebase the code quality tends to degrade, accumulating technical debt. Following the boyscout rule, we should mind the quality with each commit. Technical debt is resisted by continuous refactoring, no matter how small.
 
 How
 
-* With each commit make sure it does not degrade the codebase quality
-* Any time someone sees some code that isn't as clear as it should be, they should take the opportunity to fix it right there and then
+* With each commit make sure it does not degrade the codebase quality.
+* Any time someone sees some code that isn't as clear as it should be, they should take the opportunity to fix it right there and then.
 
 Resources
 
 * [Opportunistic Refactoring](http://martinfowler.com/bliki/OpportunisticRefactoring.html)
-* [Clean Code: A Handbook of Agile Software Craftsmanship](http://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
diff --git a/index.md b/index.md
@@ -21,6 +21,7 @@ The list was inspired by [The Principles of Good Programming](http://www.artima.
 * [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)
 
 ### Inter-Module/Class
 
@@ -359,3 +360,20 @@ How
 Resources
 
 * [Interface segregation principle](https://en.wikipedia.org/wiki/Interface_segregation_principle)
+
+## Boy-Scout Rule
+
+The Boy Scouts of America have a simple rule that we can apply to our profession: "Leave the campground cleaner than you found it". The boy-scout rule states that we should always leave the code cleaner than we found it.
+
+Why
+
+* When making changes to an existing codebase the code quality tends to degrade, accumulating technical debt. Following the boyscout rule, we should mind the quality with each commit. Technical debt is resisted by continuous refactoring, no matter how small.
+
+How
+
+* With each commit make sure it does not degrade the codebase quality.
+* Any time someone sees some code that isn't as clear as it should be, they should take the opportunity to fix it right there and then.
+
+Resources
+
+* [Opportunistic Refactoring](http://martinfowler.com/bliki/OpportunisticRefactoring.html)
