It is not unimportant to regard it as a basic quality. On the contrary, it is the most basic and important foundation for a programmer to settle down. It's nonsense to say that senior programmers are loners. The strength of any individual is limited. Even a genius like Linus needs to form a strong team to create miracles. It's inconceivable for the world's masters who write the kernel for linux without the spirit of cooperation. The lone ranger can make some small software that can make money and make a small fortune, but once he enters the R&D team of some large systems and enters the task of commercialization and product development, people who lack this quality are completely unqualified.
Step 2 record habits
To be sure, senior programmers never write documents. Good documentation is a very important part of the formal R&D process. As a code programmer, it is normal to spend 30% of working time writing technical documents, but as a senior programmer and system analyst, the proportion is much higher. Without documents, a software system will lack vitality, and it will encounter great trouble in error detection, upgrade and module reuse in the future.
3. Standardized and standardized code writing habits
Like the rules of some well-known foreign software companies, the naming of code variables, the format of comments in the code, even the indented length of nested lines and the number of blank lines between functions are clearly defined. Good writing habits are not only helpful for code transplantation and error correction, but also helpful for cooperation between different technicians.
Programmers (English programmers) are professionals engaged in program development and maintenance. Programmers are generally divided into programmers and programmers, but the boundary between them is not clear, especially in China. Software practitioners are divided into six categories: junior programmers, intermediate programmers, senior programmers, system analysts, system architects and test engineers.