>Actually, it does. Often, when you get the code working correctly, it's a mess and needs refactoring. If you stop when you get the correct result, it may not be maintainable. I once read a quote from a very famous name in the industry (I have forgotten who said this and cannot find the quote now), but is something along lines of, "When you get the code working, rewrite it so it looks like you knew what you were doing all along"
>
>
>>However writing proper code does not seem to be really connected to the problem I am bringing out.

Correct, but not my point at all.