People who are deeply maintained by the project, is it easy to produce such a fantasy --- If this is a more pure OO project, and the object model is very elegant, the project's maintenance will be much easier?
Perhaps this is the case, I also like this, now getting awake: Time is always urgent, the ability to design and developer is always very similar to "Masters", and the well-designed OO is also easy to become a ironboard surface. There is no power to change the demand.
The system is not necessarily good to go, and it is most important to create value for the user. Qianqian is a system in my eyes like a garbage-like system, users have been used in more than four years, and the number of branches has developed from nearly 20, and there is no unreasonable or loopholes in the system. The control and operation make up, although the user is not easy to use but always throw away.
What kind of system is determined by the development of business and company, a company that survives in a sketch, a system that meets the basic needs of the basic demand can meet the needs of users; if Qian is developing to more than 100, obviously The user must not throw away the old system.
Based on the above reasons, we know that there is a place to handle it, but in practice, the processing plan may be the best, and should not be picked up. Perfect. Of course, we must realize that this is not appropriate but needs to do this, nor is the realm of general design developers.
