[Reply to " 1024 " and send you a special push]
Sometimes when you're doing this job, after a while, you start looking forward to another job. Either a promotion in a position, or a change of profession. But people may often feel that way: Well, the original job is actually a better fit for me. Sometimes, further promotion or promotion, etc., only see the bright side of others.
Recently, I changed jobs, from a programmer who only focused on coding before, to the leader of a project and a team. The change of position and role made me doubt my own abilities, and sometimes I even thought: Well, it’s better to be a programmer who can only write code.
Talk about the discomfort caused by job role change
To be honest, the change of a job role will definitely bring a lot of discomfort at the beginning. After all, different positions have different responsibilities and jobs. It is normal to feel a little uncomfortable at first, but if this feeling persists for a long time, it still refuses to recede and never fades, which means that your ability is not enough to support you. Your dream, your responsibilities, your position. Come on, let's talk about the discomfort I felt at first, right?
There are many things, not a single one
After the job change, I am no longer like a programmer, just thinking about how to implement this function, how to make this effect, how to improve performance, and optimize code? Just like a programmer, just focus on the code, how specific, how good, no matter how hard and tired, it is just this one thing, and as a team leader, you have to do a lot of chores, consider the implementation of the product, and consider the overall Requirements, pay attention to the progress of the technical team to realize the project, and coordinate the cooperation between the teams. Communicate with leaders, report the progress of the project, and be responsible for them from the top to the leader and down to the team members. The promotion of the position means that the responsibility is great, the responsibility is great, and the pressure is naturally great. All kinds of chores, trivial things will make you upset.
be accountable to the team
In fact, we have to be responsible for the team, which mainly refers to the responsibility of the team members. After all, these people are the team that I pulled together, and I am also a programmer. I understand and understand the simplicity of our programmers. In this Internet, mobile Internet With the rapid development of today, many bosses use programmers as tools, and use programmers' simplicity and single-mindedness to deceive programmers. This kind of thing is not uncommon in our industry.
As the leader of this team, I am really under a lot of pressure, because I hope that while the team's technology can be improved, the treatment and benefits must be good, at least not hurt them. We must always safeguard their interests, and do not want them to lose money because of my problems, or the problems of the project, or even the problems of the boss.
be responsible for the project
As a team leader, while in charge of the overall team, you should also be responsible for the entire team's projects. The project is promising and valuable, so that you can bring better treatment and benefits to everyone. As the person in charge and department head, you must always think about the prospects, operations and market conditions of the entire project, always understand the feedback from users, communicate with operations and products, and coordinate the formulation of plans and strategic goals. Thinking about how to make this project better?
How to solve
When you encounter a problem, you have to think about how to solve it? For the tedious work and complicated affairs brought by the position, you have to learn to make a plan, make a list for yourself every day, and do it step by step according to the plan. Even if you are in a hurry, you should proceed step by step. Here we need a mental adjustment, don't delay more time due to anxiety and anxiety all day long.
As the leader of the technical team, in the process of technology selection and project development, we should consider some problems encountered, even if we help them to judge in advance, and try to understand some solutions, the specific solutions and implementation should be left to them. Realization, which can not only predict and save efficiency in advance, but also allow people in the team to learn technology and knowledge and improve their capabilities. And you should communicate with your boss, take some incentive measures, and get some basic benefits for programmers.
The project is actually the core of the entire team and company. If the project is done well, it will be valuable. As the person in charge, don't just listen to some opinions on products, design and operation, you should learn to integrate these suggestions, think clearly and think clearly to determine the needs or problems, and find ways to modify and solve them. In short, let the project become more and more Okay.
Summarize
I have complained and complained so much, not that I am really complaining, I am recording and reflecting on myself. Although for me, I still like the programmer who is dedicated to coding, but I also like this kind of challenge. If you ask me 10 years from now, do you still want to be a programmer? To be honest, I prefer to be a programmer than department leaders and team leaders. After 10 years, I still want to be a programmer.
Having said that, I have to extend a topic, which is a misunderstanding of programmers in China. It is said that programmers eat youth food. At this moment, I want to say something dirty:
This is pure fart.
In fact, capable older programmers are more popular. I saw the left ear mouse on Weibo a few days ago and also talked about this topic:
And I also stated my attitude:
I feel the same, in fact, technical management should also focus on technology. Moreover, the age capitalization code is very good, the research is in-depth, and the experience is rich. To be honest, there are generally two types of people who do technology management. One is: they are really good at technology, and they are forced to do so, but they are still very modest in researching technology, and the other is: technological development has encountered bottlenecks. After that, I thought of a way to improve management, and then the technology was just like that, and I liked to despise people.
Therefore, I would like to say: Sometimes, you must focus on technology, and when the technology reaches a certain level and ability, you can support your management dream. If you are not skilled enough to study the technology well and focus on how to get into management, then you will also encounter the problem I mentioned earlier: when your ability is not enough to support your dreams, you will be very tired, and you may be able to achieve Disgraced, even a gray nose.
Manager or Programmer? What exactly are you trying to do? Anyway, I don't want to be a CTO who doesn't write code (CTO does not necessarily have to write code, CTO who wants to write code is just my will and idea).
Technology, workplace, industry observation, everything is here!