Author | Tangmen Hierarch
Produced | Program Life (ID: coder _life)
Browsing Medium today, I saw an article that directly shouted "Technical person in charge, please stop writing code". I took the train with my family members at night, and I couldn't help discussing this topic together.
The article said that the hardest thing about becoming a Team Leader is to understand that "you are no longer a real developer". Programming and managing at the same time tends to cause you to burn out so much that you end up doing neither job well.
Most development tasks require a high degree of concentration and focus, which is incompatible with team leadership. When various meetings and phone calls continue, it is very difficult to think about how to write this code.
As a Team Leader, if all you think about is the function you just wrote, it will be difficult to answer questions from team members or customers.
Being a good manager means giving up the habits that make you unproductive, even if that includes giving up writing code.
On the other hand, human energy is always limited. If a lot of time is spent on development, then there is no time to do the work of being a Team Leader. This time often has a negative impact on the team.
So for TL, what to do?
Six-character motto: "consultation", "guidance", and "assistance";
Do Code Review to help the team solve challenging programming problems;
Keep your brain sharp by looking up the road, reading technical articles, keeping up with the latest tech news and trends, and solving small programming challenges for yourself.
I believe that for many developers, writing code will always be the purest and most joyful thing. Today's successful entrepreneurs such as Lei Jun often miss the days of writing code. But after writing code for a few years, when we gradually become a technical manager, we often become very uncomfortable, because we used to be an excellent independent contributor who could write excellent code, but now we have become a technical manager, leading With a team, it may be farther and farther away from writing code on the front line.
So, when you become a Team Leader, do you still need to write code?
After reading this article on Medium, I tossed this topic to a family member who is also a programmer, and the family member shared his opinion with me:
Team Leader can be divided into two types according to the attributes of the company's products - business type and technical type.
For business-oriented products , the Team Leader needs to pay more attention to the business. At this time, the work of writing code needs to be handed over to front-line engineers. This type of product is more about business needs, and the requirements for technical capabilities are not so high, which can be handled by front-line engineers.
At this time, Team Leader is more to control the pace of business development, to help front-line engineers to rationally sort out business needs and priorities, and to help front-line engineers quickly implement and realize product requirements.
For technical products , Team Leader still needs to write code. Of course, this is not just about writing code, the whole project architecture and technology selection are the core focus of TL. Technology is developing very fast, TL needs to have a high learning ability, and to verify itself in writing code.
A good project architecture is the technical ability that can only be developed through countless tempering and countless code tempering.
So, friends who read this article, what is your opinion? Welcome to leave a message and let us discuss together.
"New Programmer 003" is officially on the market, co-authored by more than 50 technical experts, a collection of technical books for cloud-native and digital developers. The content has both development trend and methodological structure, more than 30 well-known companies such as Huawei, Ali, Bytedance, NetEase, Kuaishou, Microsoft, Amazon, Intel , Siemens, Schneider and more than 30 well-known companies such as cloud native and digital first-hand practical experience!
