Personnel management:
1. If you want to influence people, you must be able to persuade them. (Administrative means and interest incentives can also convince people, but you need to make them believe in your authority when facing technical staff. Technicians, especially senior technical staff, have temperaments like intellectuals, and the stimulation of administrative means often produces the opposite. Effect)
2. A "grassroots" approach to persuading others: 1. Overall, his views are pretty good; 2. His way of doing things is bottom-up, not top-down 3. He is always Can take the lead in doing things in person to win the trust of others 4. He has enough patience to wait for the opportunity to come (before there is enough status and power, the Huairou policy can be adopted)
3. What really matters is what they do themselves, not what you do (except for the environment and atmosphere you create)
4. As an expert, the important thing is not to tell others what you know, but to know what kind of questions you should ask and use your knowledge to solve the problem at hand. As an expert, your role is to provide informed, actionable direction. (Individualism, claiming that one is not an expert, an expert cannot know all the solutions to the problem, but can provide reasonable guidance)
5. Proper surveillance does not mean distrust, but rather a keen interest in their work. If you don't trust your employees, you won't be able to get them to work wholeheartedly, and you won't be able to unlock the enormous creativity and potential that tight teamwork can bring. (Leaders are not omnipotent and cannot help their subordinates to solve all problems. Sometimes proper care is just emotional relief)
Life experience:
1. The legend of overnight fame is easy to lead people astray, and the legacy is not shallow. If you're going to do something completely new, be prepared to fight a protracted battle. (Be prepared to lose money and keep throwing away designs that don't pass the test)
2. The key is to practice diligently: not simply repeating over and over, but constantly challenging tasks that are slightly beyond your ability - try hard, and evaluate your performance as you do it and afterwards, and then Correct mistakes and repeat. (Keep an open mind to what you don't know)
3. The important thing is not the experience itself, but "studying hard", that is, to constantly challenge things beyond one's own ability... The main value of training is to find weaknesses and improve them in a targeted manner . (This is a big difference between professional training and self-training. Self-training is usually not as targeted as professional training, and it may remain in place for a long time)
4. Study theory at night and work on programming during the day - this combination works especially well. Most software courses just let you "listen" and "see", ignoring "do" and "review", but these last two are the key to growth and skill improvement. ("Learn" and "Do")
5. Excellent programming books stand the corrosion of time. It transcends the choice of programming language, development environment or platform and is indelible. They don't stop at telling people how to do it, they explain why. There are 5 great programming books that every working programmer should own and read. (This passage tells us how to choose a really good book)
6. Self-motivational advice given by others, no matter how well-intentioned they may be, reading them by itself is not a substitute for doing your own thing well. The sooner you understand this, the better off you will be. ...love and practice the basics so that every time I do better than before. Over time, quantitative changes will lead to qualitative changes, and success is a natural thing. But you have to be patient. Practice has proved that behind the overnight fame is many years of hardships, and even requires decades of hard work. It's not a sprint, it's a marathon. (Gather up the courage and confidence to solve problems in action)
7. Talking and writing are very different. Conversations are often loose, disorganized, or even chaotic. On the contrary, writing creates a storyline and structure that helps people understand what has happened and find solutions faster. In conclusion, talking increases the feeling of confusion, while writing is a more systematic, problem-solving approach. (Good memory is not as good as bad writing, and what is written is always more organized and closer to the essence of the problem)
8. When the child wants something that we don't have, parents often explain to the child why we don't have it. But it often turns out that the more we explain, the less the child listens. Sometimes children can more easily accept reality once their desire for something is understood. Listen, repeat their words, and indicate their emotions. Then the child will find a solution on his own. In fact, children are willing to hear the real thoughts of their parents. By expressing our feelings, we become more sincere without hurting others. (This communication method has been proven to be equally effective when communicating with adults. Learning to listen and understand the other person's emotions can ease emotions and promote consensus.)
9. Diligently practice basic skills (many master-level tasks have been insisting on practicing basic skills)
The above is excerpted from the book "Programmer's Cultivation - From Excellent to Excellent", the blogger's own understanding is in brackets