3 ms·
1. The quality of your work as a developer has no bearing on the quality of your work as a PM. It's a different skillset altogether and you may or may not have
by beforeolives 6y ago
1. The quality of your work as a developer has no bearing on the quality of your work as a PM. It's a different skillset altogether and you may or may not have it but your experience as a developer is only an asset when applying to be a PM. Whether you decide to go in that direction is a personal decision, but you should do it because you're interested in that kind of work, not because you think that your software work is subpar.
2. You don't need to take a break. You can incrementally improve on the things that you know that you're doing wrong at your current job and improve while you're still there. Since you're already aware of a bunch of them, it shouldn't be too difficult to improve on them over time.
3. You may or may not be too self-critical. The way to find out is to prepare for interviews for a bit and then try out a few. Don't disqualify yourself, let other people do that.
- BitwiseFool 6y agoAdding on to this, the kind of "hacky" code you produced while freelancing or working with small companies may have been entirely sufficient for that kind of problem. Now that you're a programmer in a much larger institution the way you code will need to change. It's going to feel very foreign to you for the first few months. The processes and patterns are almost entirely different and it's okay to take a lot of time to adjust.