From developer to PM?

Question

Project management

Hello. The situation is as follows: for half a year I work as a front in one good company. During this time, he was able to establish himself on the good side. Participated in several projects from which there was very good feedback about my work as a virgin. The frontend suits me just fine. There is also a desire to develop towards the backend.
I have good English and fairly good communication skills (actually, this manifested itself during interviews for projects, when colleagues saw how I can "sell" myself). Recently, the authorities have increasingly raised the issue of directing me towards project management. I am also interested in this direction, but the comfort zone is holding me - a favorite and interesting front, which, as already written, is going very well.
But, in the end, given that both directions attract me, I am inclined to choose the path that has more financial prospects. Dear visitors of the site, share your opinion, what is more profitable on average at a distance? What are the pros and cons of project management compared to working as a developer?
Thank you for your attention.

Answer 1

In my personal opinion:
1. Working with people (project management or department management) is more interesting, but much more difficult than writing code. People don't forgive mistakes...
2. You'll have to let go of development competencies and acquire new ones. This is not easy and at first you try to "sit on two chairs", but this only hurts. Ready?
3. S/n is secondary. Indeed, a good developer can get more than many RPs. IMHO it is necessary to choose what the soul lies in, only in this case you will develop harmoniously.
4. Don't think that RP is just meetings and planning. At some stages of the project (initiation, completion), the RP works more than the rest of the team members.
5. Culture in the company. If the management system in the company is not mature, then it is worth thinking three times before taking responsibility for the result, which may not depend on you. For example: You were appointed a RP, but they don’t give you real resources (people are constantly diverted to other work by their direct functional managers). The work will be reduced to "fighting windmills" (with an incomprehensible outcome). In such conditions, it is better to be responsible for yourself and your work (for example, to be a developer).
6. Developers now have an amazing opportunity to work remotely (imagination of some Thai beach with a hammock and a laptop). RP has much less such opportunities.
7. The RP really has more opportunities than the developer to climb the career ladder. Whether that's good or bad is up to you. The higher you climb, the more difficult it is to find a job :)
Shl Always, when making such important decisions, I try to proceed from the principle "it is better to do and regret than to regret what you did not do." )) I'm not hinting at anything, I'm not calling for anything))

Answer 2

The average PM gets no more than a good developer. But the responsibilities are completely different. People skills in general. You can become a PM if it’s right here at all. Then there will be a chance to get higher and get more.
Roughly speaking, an ordinary developer will never grow up to be the CEO of a company, but a PM, in principle, can. Only here the competition will be hoo.

Answer 3

One of the advantages of a good PM, in my opinion, is that he does not have to work only in IT. If desired, he can apply his skills in other industries. Compared to the front, the PM doesn't have to keep an eye on the zoo of frameworks that pop up quite often.

Answer 4

Well, you compare the salary of the PMA and the developer in your company, the
PM gets a lot when he works for himself and it seems to me twenty percent more than the developer in the company