If the old code specification good maintenance, product do good, why should recruit people to maintain?
If the old code is a mess worse, lack of documentation, notes, the maintenance headaches than development,
A finished product bugs don't change for many years, product design, team management may have a problem,
For maintenance personnel, the Bug is more or less good? If you change the bugs out really, is not far from the packing?

My company now is to maintain a heap of more than a decade old code, called research and development, as well as maintenance, the company itself is a kind of abnormal condition, work at ordinary times there will be some abnormal phenomenon, want to jump out, but I don't know if this is a common phenomenon, it is said that now do VC/MFC are generally maintain old products,

CodePudding user response:

No matter what the development environment and development language, has this day in the morning and evening,

CodePudding user response:

CodePudding user response:

I now use MFC, digging holes, buried themselves,

CodePudding user response:

MFC client software or to use, as long as do except for the web

CodePudding user response:

I love MFC

CodePudding user response:

Continue to develop new products, and is still comfortable!!!!!!

CodePudding user response:

reference 1/f, zhao teacher reply:

no matter what the development environment and development language, has this day in the morning and evening,

makes sense,

CodePudding user response:

Maintain with MFC all is not, as the foundation of our company's new software is based on the old software, in order to save natural resources is to get the old software code refactoring once became a new,,,, then a new software and new features, they need to continue to use MFC based on the development,,, so still useful MFC to write new products the company's

CodePudding user response:

Still use MFC to develop new products