Today, the task is allocated, because of the time relationship, a change in the module I have implemented, you need someone to help, I used the module that was completed three or four days, the person who accepts the task said "I am willing to use day time to rewrite".
Ten kinds of common statements need to be expressed in plain text. I divide the report into multiple locations as an object. The entire report defines the formatting of the base class to format the data. Ten subclasses determine their respective formats. What you need to display, implement the most important framework structure with Factory and Template Method mode. This is mainly due to many types of reports, and the format and content requirements are quite unclear, from the perspective of maintenance and expandability, and the personal tendency to select this implementation.
Colleagues intend to adopt process chemicals to wrap the document spaces and put together the way, this is due to his previously doing a similar implementation. I have seen that code --- the report is a type, the format is early, and the complexity of the typesetting alignment is not very high.
I can't imagine that the implementation of his implementation will handle the ten types of maintenance. How bad maintenance is written. He may also not understand the need for inconsistency has made complexity is completely two levels. I may not understand what is the realization in his mind, maybe he really can realize it, but PM thinks it is impossible, and later PM has made two functions for half a day, basically solved the problem (To solve the problem from the root), use GDI to get DC, get the width of each letter ..., and these code is executed on the server side, Faint!).
The most essential reason I think is that people don't have a cold about OO, just in the example of "DDD" inside Bus-Rule-Net Example, he chose the former, I chose the latter. Can't help but remember that the previous company's Mole project, the colleague told me that people who took hands did not dare.
I often consider maintainability, but for those who really maintain code, my code is like the least maintenance, interesting! I studied ORM OpenSource Obj.Net, I didn't dare to move, the first is mine The study is still not thorough, and the second is no one can give me a closer explanation of the structure and logic inside. The designed person is always carefully engaged in the system, and the whole structure is familiar with him, and he will maintain and expand its own advantage. But changed a person, if it lacks OO practice, if there is not enough high-quality document, the creator can't tell it personally, then, the reference to MZhou is "simply a disaster".
For managers, you need to play the biggest advantage of everyone, rather than let him fully show disadvantage, of course, the exercise is another thing.
