Companies have this ridiculous idea that you have to either be a PM or a developer but you can't be both. Virtually everybody in an organization except developers wants to reinforce the view that developers are just dumb coders who's only purpose is to implement the whims of everyone else in the company as fast as possible. Every PM thinks they would be successful if only they had more devs to boss around. Becoming a developer is not going to be like you think.
Even as a former PM, PM's at your company will try to exert power over you if you are a dev. They will be backed up by executive management, board members, investors, the media who all have an interest in maintaining this outdated view of the programmer who takes the specifications and simply types in the code. Why not fire PM's and just hire PM's that code? PM's don't like that, executives (who don't code) don't like that, even the janitor doesn't like that. Nobody likes that except for devs and devs have no power in companies because of self reinforcing old school ideas about job roles.
"Companies"?
The model you are describing is dying a speedy death IMHO.
The only PMs left where I work are quite technical and do manage to join the dots between projects economics, office-politics, and engineering.
Needing a PM is an indication that either something is very new, or is going very wrong.
May I advise you to look for employment somewhere not going down the drain?
Even as a former PM, PM's at your company will try to exert power over you if you are a dev. They will be backed up by executive management, board members, investors, the media who all have an interest in maintaining this outdated view of the programmer who takes the specifications and simply types in the code. Why not fire PM's and just hire PM's that code? PM's don't like that, executives (who don't code) don't like that, even the janitor doesn't like that. Nobody likes that except for devs and devs have no power in companies because of self reinforcing old school ideas about job roles.