Overtime is an eternal topic for programmers. Another term is closed development. I think everyone is familiar with this. There are also a lot of discussions about overtime. Let's take a look at the views of most programmers. But today I don't want to discuss this question. I want to talk about another topic: What is closed-end development and there is no standard answer, but let's take a look at how it actually came about.
What is closed development?"As the name suggests, closed development is to shut down a bunch of 'looping' programmers and knock on code day and night ." This is the simplest and most intuitive statement, but it focuses on being closed. As for whether programmers are pitiful, it is worth exploring. Someone asked, "Who in the world prefers to work overtime ?". Answer: "workaholic + Boss ". I don't want to work as a workaholic, and I don't want to work as a boss, so I don't like to work overtime. But there is a bit like closed development. One idea is that "closed" means long-term overtime. Those who hold this idea will feel strange. I don't like to work overtime. How can I like to close it? There are two types of closed development: vicious closed development and benign closed development. The so-called vicious closed development refers to the long-term continuous overtime in a closed environment, the serious point is ELE. Me Eating, tired, and lie down for a while, both physical and psychological environments are harsh. It can be said that this closed development is an advanced form of overtime. The so-called benign closed development refers to the fact that developers work in a relatively quiet environment and work in eight hours a day. They can enjoy full meals and sleep, improving work efficiency. In comparison with the above, it is simply a heaven and a hell.
Who like to closeNow I have gone through the development process of five or six projects, large and small. I can say that I have seen both of the above closures. In contrast, benign closed development is much happier. The difference is self-evident. As for who like to close it, we will discuss the situation in detail. For the first type, it is estimated that only the boss will like it. For the second type, most people who may want to work efficiently will like it. (The analysis results are not supported by large-scale statistics.) This involves a question. What can be caused by blocking? Is it true that people can bring efficient or high-volume work results as they wish. You don't have to worry about the vicious closed development. The morale is low, the quality is not guaranteed, and the project is usually postponed, unless you put a lot of gold bars in front of the programmer-with great material interests. Its side effects are very obvious. Benign closed development means something, and it sounds good. However, its disadvantage is that it reduces employees' sense of belonging to the company and is easy to build cars behind closed doors. In fact, both vicious and benign closed development are unhealthy software development methods.
Who is the fault?As mentioned above, the core of closed development is closed (like nonsense ). Why is it closed? The key issue is self-confidence. First, like the reason for overtime, when the schedule is tight, the supervisor often proposes overtime or closed work to relieve the pressure on the schedule. At least intuitively gives people the feeling of adding a part of extra person months. This is the inconfidence of the supervisor. Second, the traditional culture of enterprises. Some enterprises have experienced many battles in the Process of small-scale to large-scale development. For the Decision-Making layer of the company, the most unforgettable thing is the good time for everyone to suffer together in the early stages of their business. Based on these sweet memories, this kind of corporate culture is finally formed. Due to the inadaptability to the status quo after development, we did not find a set of effective theories and methods suitable for large-scale software engineering. Therefore, we would rather trust the "soil" approach adopted in small scale. This is the inconfidence of enterprises. Third, employee compromise. The heavy specification of documents, lengthy departmental processes, and non-human management systems have caused many objective factors to make technicians unable to work with peace of mind. Since the company's big environment is like this, everyone has no ability to change anything. There is no way to apply for a closed environment and establish their own ideal environment. This is the inconfidence of employees. In the end, these problems cannot be attributed to a person. Developers cannot blame the boss or the boss blindly, but cannot lament that the executive power is not enough, or the supervisor cannot be jealous of the developer. The problem lies in the transformation of Chinese IT enterprises. As we all know, the vast majority of software enterprises in China are small and medium-sized enterprises, and many have encountered a management bottleneck in their development. On the one hand, it is a bright foreign enterprise financial statement, and on the other hand, it is a "wonderful" tradition brought about by the Small Business period. It is difficult to choose between the two. Where should I go? My personal skills are limited. I can't analyze the Tao here, so I have to wait for many Chinese IT colleagues to explore it together ......
