Do I need to write code today?

"Can the manager still write code ?" If you have just been promoted from a technical development position to a management position, this will be a problem that has been very hard on you for a long time. If you have done a good job in technology and are a "master", you should be more entangled. Maybe you are struggling every day: "Do I want to write code today ?" Before discussing this issue in depth, I would like to share my personal experience with you ~ I have been working in S for five years. When I first joined this company, my position was Sr. Software Engineer. Considering my strong technical background, the company has made me stand-alone. I want to recruit new people and build and develop my own team. In the beginning, I was single-handedly writing code... Later I recruited two people and took them together, but I still took the lead. Then I made a bigger project and recruited two more people. Gradually, the work of communication and coordination is too much, but I still insist on writing code... Due to the internal organizational structure adjustment of the company, the ownership of the original project should be transferred to others, and the original team members should also be merged to other teams. Instead, I should establish a new team, responsible for the development of an underlying module with strategic importance. Two new people were recruited, and two more were recruited. A new team of four people was quickly developed. At that time, I still write code... The company reorganized again and assigned me the application software development team based on the underlying module. As a result, the number of subordinates reached 7. Since then, I began to write no code. But I am not far away from the code. I am still reading the code, doing code review... One year later, the company reorganized again, and the team of the underlying module was drawn out, and I also accepted a new mission, start to create a web service team that will play a key role in the company's future development strategy... my current position has become Sr. engineering Manager. My current status is: "basically" no code is written. Why is it "basically? Because I sometimes participate in the work of the application development team and help them fix bugs together. However, these tasks are irrelevant, such as modifying strings, correcting some simple logic, and so on. I am a C ++ developer, and they use C #. Net for application development. This objective factor makes me lose technical leadership in the project, so I am not involved in the early development tasks and will not modify their Code . I once had a hard time deciding whether to learn C # to better control the project. But I did not do that in the end. Because I have a good team to support my work. At the same time, I also want to verify that if I do not have a role as a technical expert in the project, can I lead a good team to complete the project. It turns out that I can! Many managers transferred from technical development posts are stuck in the Code and cannot extricate themselves. Why is this happening? Why is it so tempting to write code? I think it's all about inertia! Writing code is indeed a sense of accomplishment, and this sense of accomplishment can be easily achieved in the way you used to be good... Actually, this is a trap! You need to understand that after you have done the manager, your responsibilities have changed a lot. Writing code by yourself is not the most important. It is important to make a project. When the company's senior executives hand over a project to you, they are concerned about whether you can lead your team to deliver the product on time without worrying about who is writing code; they are more interested in results... To ensure the project is successful, there are too many things to be done by the manager! If you have arranged a large number of development tasks for yourself in the early days, and the results are too late to do, it hinders the process of other team members and even the whole project process, when the task is handed over to others in a hurry, it is estimated that the person who receives your job feels bad. "You shit, others wipe your ass ..." Once on LinkedIn. com, an executive commented on another executive as follows: "... He's a brilliant and versatile executive that is not afraid to get his hands dirty with coding, if necessary. "See it! In the eyes of laomei, if you are still writing code as a manager, it will make your hand dirty... Based on my personal experience, the manager can write code while protecting the interests of the project, but do not write it as much as possible. As a manager, we should consider training team members and give full play to the team's strength to complete the project well. Don't let yourself assume the "hero" role as before. Now that you have selected the management path, you must keep a clear understanding of your choice and follow this path. If you used to be a technical expert or expert, what you need to do now is to remove this halo... "Do I need to write code today ?" In fact, the question should be "Do I have time to write code ?" "If the code is written, can I make sure it is not a blocker or risk of the project ?" There is no standard answer here. Because each person's personal situation is different from the project situation. However, I can summarize it and give it a reference for beginners:
1. If your team has only 4-5 members or even fewer Members, you can write code. This will bring you closer to your team members.
A. if you write code, try not to stay in the Key Path. Cultivate team members and give them enough room for growth.
2. If your team has more than five members, try not to write code. Because you cannot guarantee the development time.
3. If you are responsible for two or more products at the same time, and the functional differences between products are large, you should not write code.