People are poor long or tired, will SB

People are poor long or tired, will SB
Poor and not changing.
Tired and don't know the summary

The so-called OOP, but the world's understanding, summary and expression

General structure of the Program (architecture) idea
Modularity: People are a module, forming an organizational module, forming a company module, social module ... From a thin look, atoms, molecules, organs, people ...
The problem area determines the particle size of the module
A radish a pit, radish can be replaced, because radishes are similar
and decoupling: For example, any employee of a company who has things to look directly at the boss, the boss must finally be crazy, this is the coupling is too high
Another talk about layering: the soil boss after the certification summary of the next, so there is a hierarchy, with the pyramid ... The result of a natural selection

How to describe the organization (or other object, OOP) using the structured thinking of the program
Layered look:
The boss said it was impossible for me to do all the work, I had to organize a team to lead everyone to work with me. Thus formed the core leadership.
Core business Backbone said, all the things let me do is impossible, I have to organize a team to lead everyone to work with me. Thus formed the core business backbone layer.
The recruiter says, do it!

Pyramid, fan structure, influence

Programmer vs Program Designer

Google's ' three realms ' division of programmers via Android
Android's classic structure: Kernel layer, app framework layer, app layer

Android's stereotyped writing
The life cycle of four components

People have the ability to size the points
The ability to define the three realms
In a field of specialization, specializing in a field.
Soy sauce, eliminated.

Programmers do not be poor or tired, it will become SB.

People are poor long or tired, will SB