Do I need to be a programmer to manage projects?

Question

Project management

Comrades, please help me stop floundering in the world of marketing.
I am an internet marketer with 2 years of experience. In my free time, I do freelance layout, a bit of website design. I work as an Internet marketer because the pay is good, but this job is not for me. For myself, I realized that I did not want to go there at all. I want to try myself as an IT project manager. I read on the Internet that programmers are unlikely to listen if I am far from programming. That the path to the PM goes through the programmer->teamlead->PM .
I started to study javascript, in principle, so far everything is going pretty well, but there is still an abyss of information ahead. No, I like everything, js is an interesting language, I work on this resource.
Attention question:
I’m doing some kind of garbage and I need to immediately delve into the study of skills for the PM, become an assistant, or do I need to tighten up the programming and yet the path goes according to the scheme programmer->teamlead->PM?

Answer 1

The manager and director at the company where I work are not deeply "dedicated" to programming, but in 90% of cases we find a common language quickly. If something is not clear, we explain it in simple language and thus begin to better understand the task ourselves...
I think this is the norm, and if you also know the language / and programming - generally super! The most important thing is patience and not to show off)

Answer 2

Being a programmer is not a prerequisite for becoming a PM.

Answer 3

A project manager does not need to know a programming language to manage a programmer. This is exactly the same as the director of an enterprise does not need to know accounting in order to manage an accountant.
The art of a manager lies in his ability to achieve a goal with the help of available resources. And the resources of the project manager are the members of his team, including programmers. Therefore, the manager must know very well the capabilities of these programmers (what they can do), but not the programming language itself.
And yet, the path "programmer->teamlead->PM" is too long - you can "get lost" along the way. If you decide to become a manager, then immediately look for opportunities related to project management.

Answer 4

It's the same as asking "is it necessary to have successful released projects to lead the development of these projects". Yes need. Otherwise it will be like always. Management does not seek to make a good project, but seeks not to sully its reputation with superiors. And the programmers are to blame for everything, because they are "tyzhpogramist" and should be able to do everything. And the PM just came for a salary, because he is just trying to survive and he needs money.

Answer 5

Here I found a development scheme in IT (on dou.ua). As you can see, you can become a PM not only along the path of growth from programming

Answer 6

It depends on what project management is for you. Most often, under "PM" they see the illusion of control. The process goes by itself, by inertia, and people think that they are managing something. Management is as subtle a science as psychology. You can manipulate the result in a thousand ways. It already depends on the individual. Someone will do it himself, someone will delegate, someone will hire, someone will force, someone will convince not to do it, someone will postpone, etc.

Answer 7

The PM must understand what can be implemented within the framework of a given programming language and in what time frame. Therefore, in my opinion, the PM should have superficial knowledge in a large number of web technologies. It's not even so much about the knowledge of the language itself, but about the knowledge of technologies (frameworks, etc.)

Answer 8

you need to tighten up the programming and yet the path follows the scheme programmer-> team lead-> PM

this option is correct!

Answer 9

Depends on the specific responsibilities of the position.
Theoretically, PM can be based solely on the estimates given by the developers themselves, and, in fact, act only as a motivating link (+ task management), but it depends on the company. But then your competencies should be completely in the business plane. If we talk about technical PM,
he should have a good understanding of both the applied technologies and alternative ones, be able to evaluate different solutions quite accurately in terms of time / resources. This is difficult to achieve without development practice.
On the other hand, for example, embarking on in-depth js-development, you run the risk of being left with a "narrow" overview, and not understanding the problems of other technologies at all. The second factor is that the study of theory and real projects are too far apart.
Also, it is quite possible that you do not have a base for a full-fledged development, and measuring by yourself, you again will not come to an adequate estimate of labor costs.