There is how you become a manager as you call out, but what happens after? How to stay an excellent IC as you spend more time in management and become a manager of managers? Picking up a small enhancement it big once in a while can be helpful for you, but also really interruptive for the team. You can code on your own time, but that only goes so far. What are strategies to keep these qualities a manager brings who also is a top IC even after years managing and managing managers?
I struggle a lot with this, I’m trying todo some side projects to keep up but man it’s hard. I think the only way is to on a high level keep up with new technologies and best practices.
In an agile environment (the most common structure in software development) the professional class of scrum masters and analysts are often non-technical, and management is sparse and hands-off (teams are "self-organized"). Key technical decisions are relegated to senior individual contributors, allowing for CV driven development, cargo culting, and bad habits. Stories of a Microsoft VP who files a bug report and points out the line of code where the error occured could never have happened anywhere where I worked.