The second of knowledge structure of C language

The knowledge structure of C language is organized into mind mapping, for example, as seen in:

The overall idea of this picture is:

1. Hit the code with C. What should I learn?
2. To write in C better, change what to learn?

In fact. If only the hierarchical knowledge structure, the general idea is:

1. First of all, study the knowledge of this layer;
2. Secondly. To study the knowledge of the first layer above, if any.
3. Thirdly, to study the above, the following layer of knowledge;
4. Repeat step 3.

The goal is only one: to do the work of this layer (remember the goal, don't diverge.) Study other layers too deep). Give two examples:

1. The code written in C, almost identical, is in the hierarchy of the operating system. If you are writing a library, you need to understand the principles of the operating system (bottom layer) and the requirements of the application (the first layer). The assumption is that the application is written. It is necessary to understand how a dependent library works (next to the first layer). Not on the first level).

2. As a program ape, the company's personnel organization also happens to be a hierarchical structure.

   The assumption is that ordinary program apes, located at the bottom, need to know what their needs are, what they are doing every day, and so on. The goal is to make your work better.

The second of knowledge structure of C language