|
Disclaimer: Probably not highly compensated by hackernews standards (ie I'm still working), but I am well above the threshold you cite. Have been doing this since ~1993, and ... I wouldn't change anything. Had a few wins along the way You say you are a PM - have you done both greenfield (aka "primary software construction") and looking at how to deploy/tune a canned application (like Salesforce)? I think they are materially different skills. How deep are your personal tech skills? I tend to see the very best PM's become CEO's pretty rapidly, so that is one path. For me the most impact came from "rushing to the unglamourous stuff." Documentation, testing, build and deployment pipelines, security and compliance (which are not the same thing), and then building bridges to other functions, which helped me be the 'voice of the customer,' over and over again. As an IC, I've been a coder (initally perl, later c++, then python), network engineer (cisco bgp/load balancers - pre cloud era), data center manager, biz apps steward (jira, confluence, sfdc, hris), database admin. As a manager I've managed dev teams, SRE teams, data science teams, and product teams. Getting involved in sales engineering and direct customer support also helped a lot. They talk about "T" shaped people, but if you can have depth in multiple areas and have a framework for understanding black box (ie $largeVendor [ie Oracle] is used for $UnchangeableMissionCritical application - how are you going to work with it?) stuff, then you can level up from a "mere" PM to an "Agent of Organization Wide Change" |
So much this.
I'd hesitate to even call them adjacent.
Compliance is nothing more than a set of checkboxes. It won't stop your developers from writing `sql.query("select * from users where username = '" + username + "'`.