Chapter 5 personal character (Code Daquan 5)

Chapter 2 personal character

Personal Character

• 33.1 individual personality is irrelevant to the topic of this book
• 33.2 smart and modest
• 33.3 curiosity
• 33.4 honesty
• 33.5 Exchange and Cooperation
• 33.6 creativity and discipline
• 33.7 laziness
• 33.8 is not as effective as you think.
• 33.9 habits

33.1 isn' t personal character off the topic

Is my personality irrelevant to this book?
The programming process consumes a lot of mental power. This feature makes my personality very important. Programming is essentially an unsupervised task, because no one knows exactly what you are doing. We often have this experience: it takes 80% of the time to focus on individual projects, and 20% of the time to complete the remaining 80% of the work.
The boss cannot force you to become a good programmer. In many cases, he cannot even judge whether you are qualified. If you want to achieve something, you can only rely on yourself. This involves your personal character.
Once you are determined to become a good programmer, your development potential will be great. Various studies have found that the time difference required by different programmers to create a program can reach, it also finds that the time required by different programmers to debug the program, the program implementation scale, speed, error rate, and the number of checked errors can also reach.
You cannot improve your intelligence, but your personality can be improved to some extent. Facts have proved that personal character is more decisive for creating a programmer master.

33.2 intelligence and humility
Smart and modest
Smart is not like an aspect of personal character, nor is it true. Coincidentally, there is no close connection between high IQ and excellent programmers.
What? Don't you need a high IQ?
Yes, no. No one can be as agile as a computer. To fully understand a common program, you must have a strong ability to absorb details and digest them at the same time. How to focus on your talents is more important than how smart you are.
As mentioned in Chapter 1 "design in software building", Edger Dijkstra read the article "the humble programmer" (humble programmer) at the 5th Turing Award speech.. He believes that most programming work aims to make up for our limited intelligence. Programmers who are proficient in programming are modest people who know how limited their minds are. Those who have poor programming skills always refuse to accept the fact that they are not competent in their work, so that they cannot become good programmers. Admit that you have limited intelligence and learn to make up for it, you will become a better programmer. The more humble you are, the faster your progress will be.
Many good programming practices can reduce the burden on Gray Matter cells (brain) in your brain.

The system is "broken down" to make it easy to understand.
Review, review, and test are conducted to reduce human errors.
Write subprograms to reduce the brain load.
Programming is based on issues rather than underlying implementation details to reduce the workload.
Through a variety of specifications, the idea is freed from the relatively cumbersome programming.
You may think that developing a higher level of intelligence is the right path, so you don't need these programming roaders. You may also be dismissive to the programmers who use these intellectual roaders. However, in fact, the modest programmer who studies the table name is good at making up for its shortcomings. The code is easy to understand for himself and others, with fewer error pages. A development process full of errors and delays is an evil way.

 

Chapter 5 personal character (Code Daquan 5)