Root Cause of software company overtime

It should be a very common thing for software companies to work overtime. In fact, working overtime should not be an uncomfortable thing. Any company or organization will work overtime, but to a different extent, it is not comfortable.

Overtime is not necessarily a bad thing.

Why does it work overtime?

Overtime is generally the direct result of not finishing the work.

However, there may be two possibilities: one is that the tasks that should be completed are not completed;

The other is some special cases. In this case, there is nothing to say. Just do it.

In the first case, it may be divided into two situations: one is because the time order is delayed by other tasks that must be completed. In this case, we will remind people who have done their work before, then proceed;

The other is that you cannot finish the required quality tasks within the specified time.

This situation is further divided into two situations: one is that the previous provision did not really meet the required requirements, resulting in a lot of work to be done later; in this case, first, ask the question.

The other is for its own reasons. The premise is very good, and it is not done by itself. This situation requires caution, because it actually means there is still a gap between our own technology and we cannot finish our work according to quality requirements.

The reason for overtime is not just for yourself.

According to the above analysis, the reason for working overtime is not just for yourself. It may be that the premise is not very good. I have done a lot of makeup work first. Of course, what is even worse is that it takes a lot of time to complete the work, finally, I came to the conclusion that it would be better to get a new one to make up for. This is the most painful thing in the world. It is no less than a fall in love. If the time is too short, you may really want to hurry up to the end of the world, it's all over... haha, just kidding. You still have to make it happen... however, it is very important to avoid this situation. We need to be careful when dealing with these problems. If there is a problem, the author or relevant personnel should make a summary, try to avoid designing something that will force the later to re-design and write code. If so, what is the significance of the design? What is the difference between development and code workers?

If it is caused by its own reasons, in-depth analysis will generally lead to the conclusion that some technical problems are not clear enough. For a long time, I have been thinking about what is a clear understanding of technical issues? After thinking over and over again, you cannot fully interpret this concept. If you can explain any technical problem from the perspective of the designer, is it clear? However, many do not need this because there are many technologies and one cannot understand everything. So how can we prove our understanding of a technical problem? After studying a lot of things about the operating system and compiler, the answer to this question gradually emerges, that is, the principle or process of an upper-level question can be explained or analyzed from the bottom layer, that's why I understand the problem.

However, it is a pity that in this software environment in China, most of the underlying things seem not very important, it seems that only those who are engaged in research, embedded systems, drivers, and architectures that require high capabilities really understand this. I can only say that this makes a big mistake, because I don't know how to use the upper layer of the underlying layer, and there may always be errors, because there may be many upper-layer errors, and it may not be difficult to locate this problem, however, understanding this problem may not be a simple issue. If you pay attention to it, the chances of making mistakes will be reduced. Otherwise, the bug will only pile up and pile up, and it will soon disappear, it's almost the same as working overtime.

In fact, the bottom layer is not difficult, but not so many people bother to learn and understand. Maybe they only need to pull a person's point, and a difficult problem will be OK; the difference will be worse, does the company have such talents? Are they affecting the entire team? Is it still inefficient for the team to change the bug of the upper layer? Is it true that the bottom layer is laughing?

Xichen

13:37:01