The company's website was made by an outsourcing company in the early days. After programmer a took over, it felt that the outsourcing company did not do, all reconstructed again. After the programmer B took over, I found the code written by a is not easy to read and rewrite. A refactoring took one months and the development of new features was shelved for refactoring. There are ways to avoid code that often requires refactoring, or reducing the cost of refactoring.
Reply content:
Refactoring is a no-no, programmers always have to choose between good architecture and changing needs, and digest dirty code through constant refactoring. What you need to avoid is completely refactoring the process after the code is completely out of control.
Simple, don't save money, don't look for outsourcing, find some of the best programmers, it is better to recruit a team.
Anyway, you want is not good code, just a result, the code is bad you do not care about it, so no sense of responsibility and ability of programmers to screw things up again normal, but this cheap can not be accounted for.
I have seen the good code to make up the garbage, also saw the garbage code maintenance can only be reconstructed, the whole look at the wages of people are not taste.
But bosses don't have to worry about spending money on digging people out of a high-end company and checking it out by the right people. Each time the refactoring is refactored, refactoring for yourself, refactoring for the one you love: Instead of fish for fame, it doesn't have to be regular. The owner of the estimate is the boss? Pm? As a boss or PM do not know the technology, do not block the program Ape reconstruction, that is their normal work within the scope of things, all you have to do is to find a reliable main course and trust him in this aspect of the decision to stop the project our front desk will actively stop refactoring.
