As you probably know, estimating how long software takes to develop is at best challenging, and at worse impossible. Part of estimating how long something will

As you probably know, estimating how long software takes to develop is at best challenging, and at worse impossible. Part of estimating how long something will take comes from some domain expertise. I encourage you to continue dabbling in the technologies you're team uses, so what you know doesn't drift too far from what your team knows. Another reasons to keep dabbling is that you may decide you don't like project management. If you work as a PM for two years without writing any code, trying to get back into development is gonna be much harder. Lastly, as a code dabbler, don't try being a developer yourself. That's no longer your role. The occasional git commit to fix a typo or something is fine, but you don't wanna be that guy who is a control freak, always refactoring the code your team delivers. If you wanna write code, stay in development.