>Hello Nadya.
>
>>> This is the exact proverb, what everybody here except me uses as a rule. For instance, I pointed out several times about few really bad code fragments, which may give problems in any time. The answer always was this proverb and a bad attitude from the colleagues... <<
>
>Well, there is another saying: The show must go on. In a perfect world, we would be able to refactor the software whenever the software needs refactoring. But if this comes at the cost of doing business, then the business doesn't need you to refactor their software because they won't stay in business long.
>
>If refactoring this "really bad code fragments, which may give problems in any time" does not take time away from resolving more pressing software problems that the company needs to have resolved in order to stay in business, this is a different matter.

Well, fixing some of the problem can take less than 3-5 minutes, but of course, each change should be then re-tested, which takes time. That's one of the reason for such resistance. From my own perspective as a programer, my applications should be perfect, so I constantly change them, when I grasp a new idea or decide to improve some code, or whatever. However, from the perspective of my manager it may not be always needed...