From the definition of program variables to the management of leadership Layers

Currently, in almost all languages, variables are applicable to the "Global" and "local" areas. If a variable has been defined as a global variable, either it cannot be defined again within the function or process, or it has completely different meanings. That is to say, variable management has strict hierarchy and applicability in the code of the same software. Global variables and local variables cannot conflict with each other. Otherwise, functions and processes may be confused because they cannot distinguish variables.
Software is a logically rigorous knowledge product. The management of variables in the Code strictly reflects the division of duties and scope, performs their respective duties, and performs their respective duties, so there is no ambiguity.
An organization or unit, regardless of its size, is managed in a similar way as a variable. An employee has his/her own direct manager. He is used to being the top boss and has a superior. "Superior leadership" leads "Top superiors" and "Top superiors" lead bottom employees again. This is a normal form of organization and management. If the superior and the top superiors send orders to their employees at the same time, if the commands of the leaders are different, especially when they are in conflict, who should the employees listen? The top boss may affect your bonus, and the superior leadership decides your stay. This "political and political" situation will make employees feel embarrassed and at a loss!
In the real environment, this is not uncommon. There are always some larger leaders who, in order to show themselves "taking the lead" and undermine the management hierarchy, give commands directly to employees beyond your superiors regardless of the feelings of middle-level leaders, poor grassroots employees are in a dilemma. Fortunately, the employee is a person and can be swallowed up. If it is a program, it has long been an exception-fuck, I quit!
However, there are many leaders who can solve the problem by debugging the program. The employee cannot always resign because of this, right? How can this problem be solved? In the program code, local variables are used as the standard, but in actual work management, I feel like listening to big leaders is wonderful! Although it is inevitable that larger leaders are more bureaucratic, do not forget that your superiors are also led by larger leaders. Maybe the middle-level leaders may have problems when they directly intervene in the underlying affairs. Don't let the big leaders eradicate you with the middle-level leaders.
But this is not exactly the case. Maybe this is just an accident. If an employee forgets his or her boss, the employee may be removed first. How to do this depends on the understanding of employees. Employees with poor eyes always suffer the biggest loss in the workplace.

See the author's personal website: Computer Learning Network-education workplace channel: http://www.why100000.com/_articles/show_a_article.asp? Tab = tabeducation & autoid = 535