Postscript (to make up the number of words): This article talks about the "harm" caused by the process to the programmer. When the company is relatively small, there is usually no process, and the process has to be established when the company becomes larger. I used to lead a small foreign company. At that time, the company was poorly managed and changed a CEO. The new CEO used to work for IBM. He was eager to revitalize the company. He gave everyone a boost as soon as he took office. There was a staff meeting and told everyone "Although we are a small company, we are flexible, efficient, and easy to turn around. When I was at IBM, the company was very powerful, but the organization was bloated and the decision-making was complicated. Once there was something that needed approval. Can you guess how many times it needs to be stamped?" "Five times, eight times, ten times..." Everyone failed to guess, and finally the CEO revealed the answer: "A total of 28 times!" I was shocked. When it arrives, what needs 28 approvals to pass, and how low is this efficiency? Is this impossible? After two years, I also joined IBM. I stayed for seven or eight years and I have never seen a situation requiring approval twenty-eight times. I think this is either a very rare case, or I am too low-level to meet. Right.
More exciting technical comics, all in the programmers stand up