Just want to leave this here.........
Separation of concerns - Wikipedia, the free encyclopedia
all developers should follow this. I'm currently dealing with a single C# class at work that's around 3,000 lines of code. The class performs about 20 different actions. Examples:
1.) Connect to Team Foundation Server
2.) Read Excel for data
3.) Build object properties from Excel ( We are using Coded UI )
4.) Read a couple of XML files
5.) Input Data into the Application Under Test
6.) Handles all error handling
7.) Builds a HTML Report
Each one of those should be there own class.
1.) Makes it easier to add new features
2.) debug code and fix things without accidentally editing something else within the class
There's many more, but