We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I like this message very much, ohh! what's pitiful! it's 2 years ago. but I really hope the writer or someone can send VS51.exe. thanks!
My email zeeman2003@hotmail.com
A 50 times time saving is 5000%.
But that would require that the developer spends a huge amount of time playing with the code after having initially written it. If the code takes 10 hours to write, you would have to spend 500 hours with it (besides debugging) to perform manual cleanup. If that time isn't available, then you can obviously not optimize it away.
If I pick up an old project, I can normally see more than 90% of the source lines having revision 1.1 in the source repository, indicating that there are very few lines that gets modified after having been initially written. That would then indicate that less than 10% of the code lines could take advantage of any code factoring. The total gain from a tool supporting code factoring would then be quite small.
When developing a product, it can be said that each step later in the development cycle that an error is caught, the cost will have increased with a factor 10. You do not want bugs or hw errors in the released product. You want to catch them during the design phase. Twice the time invested in the design phase is well invested money. And it removes the need for a lot of code rewrites during the lifetime of the product.
It is very good to have tools that helps correlating source code with the requirements specification. But it is dangerous when people looks for the source code editors that are quickest at rewriting code. Having large needs for code rewrites indicates large problems in the development process.