two assertions

I sent a tweet, many people don't understand it, let me explain it today.

The use of time management software by programmers is the beginning of the fall; and when project managers find programmers using these things, they should reflect on their dereliction of duty. Programmers who use knowledge management software are the beginning of a downfall; technical leaders should admit their incompetence if they find programmers using them.

I have said long ago that time management software is something that programmers don’t need. The reason is very simple. Programmers need a lot of time to think, program, and debug. In short, it takes a lot of time to enter a certain state to be very useful Efficient work. As you can see, a lot of so-called efficient work is done by working overtime at night. The use of time management itself shows that programmers have a lot of work to do, which does not require any technical skills and is purely transactional. So the day's work will be disrupted by these small pieces of time. And if it is the state you have already entered, but at this moment you suddenly feel that some other things should be done, what would you do? Tell you that no matter what you do, you are already wrong. Because the right way is, you don't think about it at all. As a project manager, one of the most important duties is to ensure that programmers can work efficiently, so these piecemeal things should be rejected by him. Of course no one will say that I just want to disturb you, but there are many important reasons. For example, the leader wants to come to inspect, for example, the accountant needs to report the account, the market needs technical personnel to participate in an interview, for example, a technical management thinks that there is a problem somewhere and needs to communicate, for example, the test thinks that the time for a certain test needs to be determined, and so on. You see it is a formal and very reasonable request. But it is precisely these requests that should be rejected the most. Even lunch at noon should not be interrupted if the programmer does not ask for it. Unless a programmer's personal interests are very relevant, such as the death of a parent, such as a child sick, otherwise their work should not be interrupted.

And the next statement, many people do not understand, or simply say that many people will object. In fact, I am not against the use of knowledge management software in projects, and I believe that a project must have knowledge management software, and a team must also have knowledge management. What I am against is that individuals conduct their own knowledge management activities alone. Needless to say, communication is the most important activity in a project, so much so that writing code can be considered less important. Because the survey found that communication is the project that takes up the most time and resources. Therefore, when we are working on a project, we must first consider how to enhance the efficiency of communication. In fact, knowledge management in a separate self-learning style is not only not good for communication, but also forms an information island, thereby delaying the progress of communication. And if our learning takes place collectively, the effect on communication is not to block but to strengthen. In fact, through collective learning and knowledge management, the formation of team dialects can be enhanced, so that communication can be based on collective memory rather than language. The efficiency of the two is simply not an order of magnitude. These are the parts that process management should involve and must involve. In fact, everyone understands this principle, but it is not so simple to do. And the actual situation is also the same. I see that almost all people are emphasizing learning and knowledge management, but in practice there is basically no work in this area.