from learning programming to practical development, mistakes of ignorance are bound to occur. Even in the best projects, despite thorough testing, good documentation and the best players. Each person's limitations are doomed to be slightly inadequate in one respect. We are proud of our abilities, and we should be honest about our ignorance and mistakes. from your next task, you have a responsibility. When mistakes are made, have you ever asked yourself if you have done enough to be careful in your development process? The first is to interrogate yourself rather than blame others. This is an important manifestation of the attitude of a good person in examining the problem. Indeed, if there is a teammate's mistake or the supply side's shortcomings, then think about whether we have a second hand to prepare. People often say that computer-learning logic is precise, indeed. But we should not only stay on the level of thinking, we have to learn to do a comprehensive. Learn to prepare contingency plans, learn to back up customer important information, learn to archive their critical information and so on. It's good for work and good for yourself. Furthermore, when you are ready to tell others why you can't do it, why it is delayed, why we have problems, we must calm down and think. Can others understand what you say? and whether others will ask you something. Learn to show the conversation in your mind, even if you tell others bad news, you should deal with the harmonious atmosphere. The attitude is sincere, honest to say own ignorance mistake. Learning to express itself is the ability of a good programmer. Accept the ignorance error, perhaps this will give the first entry into the workplace of our a loud slap, the more loudly the slap, we must feel deeper.
Programmer's Way of cultivation (1)--focus on not being afraid to admit ignorance mistakes
