Google’s ten years, my cognition was completely subverted

谷歌十年，我的认知被彻底颠覆

Haizhuren website: from the network Wang Haogang Wukong Intelligent Technology 2019-02-06

Part 5

Third, the meaning of the word "management" is completely different.

At Google, sometimes engineers are difficult to manage because most people think new, have more ideas, have a high vision, and have a strong personality. At Google, sometimes engineers are easy to manage. Just encourage them to make world-class standards for a seemingly ordinary thing. They have enough excellent execution and don't need to be supervised.

It’s a different matter to have a technical manager at Google and bring a team with me in other companies. This may be related to the average level of the technical team, but it is still a matter of management.

I remember that in other companies, I spent a lot of time on development process management. Now I think that most of them are red tape, stylized, dogmatic, and the most extreme process certification like ISO9000, which makes everyone exhausted and the effect may not be much. it is good.

4hen I arrived at Google, I found a secret, more rules and regulations, and more processes, not as effective as a set of useful tools. For example, Code Style and Code Review, which used to be annoying to the technical manager, could not be implemented in three or five times. After three days of heat, everyone was guilty of violating the yin. At Google, this is not a complete system issue. The engineer who just came in did not have Readability Review, and he couldn't easily submit the code autonomously. This is a hard limit for the code management tool settings. This directly sent engineers to the jury for "re-education." Yes, it was really "re-education." Even Guido van Rossum, the father of Python, took a lot of effort to pass the Readability Review of the Python language code. Next, before submitting the new code, various static and dynamic checking tools run automatically to help you report a series of style errors, compilation errors, unit test errors, and simple logic errors. You must first follow the tool prompts. Change the low-level error again before entering the Peer Review. The entire Code Review is done in a very handy web tool, and people who write code and review code can easily interact, discuss, and even modify code online. The “mandatory” of the tool guarantees the implementation of the system, and the “convenience” of the tool minimizes the burden on the engineer's execution system, and the two complement each other. Of course, there is no lack of internal system in Google, but Google does better than other companies.

When it comes to management, the technical team at Google is actually bitter. I have handed the team to others twice, and I am happy to do some simple code work. The reason is very simple, the title is Manager, but you can't be arrogant, Google's best team leader is rushing to the front line with everyone, in addition to taking the initiative to take care of the dirty, tired, miscellaneous In addition, it is necessary to do non-technical work that managers must do, such as writing reviews and bonuses for everyone, helping everyone to apply for promotion, and talking to the psychological burden... One person does two jobs, and the effort is not good. There is no decision on the promotion of team members (this thing is also very godsome), this Manager's work, who is willing to do it, I do not like to do it. However, I don't like to like it or not. Google's quite different management is not only chaotic, but also very good. It is really amazing.

Strictly speaking, smart people are together, only need to be motivated, no management, and Google's approach mainly emphasizes this.

Please continue to see the sixth part