Here are Ten Code Clean ups that have minimum risk to the legacy environment:

1. Remove Unused “using’ Statements
2. Convert Private Data Members into Auto-Properties
3. Initialize Class Level Private Properties in a Default Constructor
4. Rename Bad Property Names into the Correct Class Naming Convention
5. Create a Region at the bottom of the page for all Private Methods as a Helper Section
6. Identify the Methods in the Class that are ONLY used in that Class and move to Helper Region
7. Replace Explicit Type Names with ‘var’ to reduce the “Code Noise” in the Type
8. Identify and Move the Value of ‘temp’ variables: Variables that are created and only used ONE Time. Move the variable statement to the One and Only One usage to improve performance.
9. Extract Helper Methods from Large Methods and place in the Helper Region if only usable in the current Type. Extract and Move to a Common Utilities Helper Type for Code reuse by the tea. Always document Common Helper Methods in a centrally located and published Knowledge Repository.
10. Extract complicated algorithms and lengthily code from Conditionals such as ‘try/catch’, nested ‘ifs’ and ‘switch’ statements.  Place in the Helper Region. This will improve performance at Run-time

The concept of the Boy Scout Principle is the Boy Scout Motto:

 You should leave Nature’s Environment better than you found it

… By not leaving a human footprint

…… And by removing any trash that someone has left

Code refactoring to Best Practices is every developer’s responsibility!

You should leave Nature’s Environment better than you found it

… By not leaving a human footprint

…… And by removing any trash that someone has left

The Boy Scout Principle gives us the directive to help manage “Technical Debt”.

Technical Debt is when code is compromised for expediency

… At the risk of the project in the long-term

Never let obvious Code Smells stay in a solution!

Any code that does not meet the Code Standards for the Project

Any code that does not meet the Code Standards for the Project

No violation examples are required.

Violations are any non compliance with the Project Development Code Standards

The refactoring list is the examples for code refactoring