Understanding object-oriented

Object Oriented Comprehension

Objects are based on real things (not abstract concepts or common metaphors). They are encapsulated and inherited to solve things laws (classes) and real applications (instances) this is the process of turning the complicated design proposition into an overall package of "encapsulation. Because this process must emphasize the induction and abstraction of the Process of things, it will inevitably increase the threshold for designing "objects". It is precisely because "class objects" have such abstract processes, therefore, it is possible to reduce the implementation difficulty of the application instance and have a large scope of application.
Many programmers understand the concept of "object" in the state of "looking at the flowers in the fog". They seem to be able to understand it, but do not know how to apply it. Only use the basic "object" provided by the system, but do not (or do not know at all) design or encapsulate your own "custom object ". It only works with tools provided by others. It is only a laborer and cannot be a real "designer.
Objectively speaking, the "Object-Oriented" design concept sounds easy to implement. I often see some programmers who think they are "proficient" in object-oriented concepts, but have never implemented the design and encapsulation of "objects". There is no lack of a sense of ridicule. If we compare the object-oriented philosophy to a palace, many people who are wandering at the door think they have long lived in the palace. In fact, this is a misunderstanding.
The significance of programming is not to use "code (or simple application system object)" to describe the requirement, but to meet the "design concept, transform original requirements into "objects" that reflect "design ideas" (design units closest to the characteristics of things) and the "object" that represents the connotation of the demand to complete the "design ".
If you want to determine whether you really understand the "Object-Oriented" development philosophy, the simplest and most direct way is to see if he has implemented the "custom object" encapsulation, this is the original intention and goal of the object-oriented concept.
The development environment provides us with technical means to design, encapsulate, and reference various "objects, on this stage, how to abstract, construct, design, and use the "object" of our own applications is a concrete manifestation of our ability to control "Object-Oriented.
Do not think that "object-oriented" is so profound and difficult to understand. In fact, it is like a "window paper". As long as you gently "poke" the following, all problems will be solved. The key is whether you realize the existence of this layer of "window paper" and stick your finger out. On the contrary, if you are not aware of its existence or do not want to pay for it, you can only see the flowers in the fog at the door of the hall.