About oo -- do not abuse it !!!

I wrote it before: It was another year. I had a step in understanding oo after countless bugs. I recorded it here so that I could smile at the beginning of my knowledge and ignorance when I looked back.

So far, (except for Software Engineering-although the next is software engineering, it is not a general conceptual document and theory) Oo has the following spirit: refactoring, principles, models, test-driven-develop. if the preliminary design is also calculated, add UML-case to analyze etc...

It is worth mentioning that, in actual development, there will always be people who want to approach "Spirit" and talk about "principles", "design-pattern", and so on. I am very sorry for this, it is necessary that all cases conform to a certain "Principle" and are close to a certain "mode ". although I think I am quite familiar with this, please remember: Do not abuse it !!!....

I remember that I talked about several applications related to "reflection" and "metadata" in one explanation, which means that dll can be dynamically called and Compare of the same type can be used, clone (when there is no loop pointer), it can be automatedCodeAfter analyzing etc..., I was suddenly asked, "Is it true? I suggest you look at the design-pattern, and there will be very interesting applications. "------- with a stick, I looked back and suddenly thought about whether to use object-name to build the" Factory "mode? _?

There is no answer to this question. I only want to guess it. But do you have to link it with the model?

Therefore, the table is intended to emphasize :"Do not abuse".