Keeping the code clean and tidy
This week I have been so busy with the ESRI user conference, I spend evening watching the podcasts. Tomorrow morning I need to wake up around 4 to go down to San Diego and work at the UC. Its going to be my first ESRI User Conference. As well as being a busy week because the UC, I have been finishing and cleaning up a project, and raises the question about how do you clean up code?
When you find a few lines that you do not need anymore, but they work, do you comment out the code or you delete it? Now think about it very carefully. You got QA or requirements telling you don't need that functionality anymore. However you know that you spend sometime working on that piece and you may need it somewhere else or worse, somebody is going to change their minds. Would you comment out the code? Delete the code? Or add the code in a special place to use someday?
Another question, do you enable the warning to let you know what public methods don't have comments? Do you make sure to comment all the classes and public methods?
What code analysis software do you use? Do you use Visual Studio 2005 Team Foundation Server?
Do you test your classes? What testing procedure do you use?
I'm not as good as I would like to be testing my classes or cleaning up, when you have so many lines of code in different assemblies and project, gets a little harder to do the clean up. I wonder, what process do you use?
Cheers
Al