> If you get interested in what you learn about the new technology, you may want to keep trying to understand it better; you may read more or embark on a personal project using it to gain more practical knowledge. As I said, it isn’t that you must stop coding. It is that, eventually, it shouldn’t be your day job anymore.
One thing that gets elided in a lot of "servant leadership" style chatter is, as a manager, you have permission to be straight up selfish. New leaders often struggle falling back into their old "inefficient" patterns of learning things but you have a team of resources at your disposal now.
You can just straight up ask a member of your team to prepare a bunch of background on the new technology and book a solid hour for them to personally tutor you through it. Sad to say but your time is more valuable than theirs and it does them no good for you to struggle at the other parts of your job because you're too modest to use your vested power. Often, teammates are actually happy to take the burden off your plate, if you poll ICs about gripes about their manager, one that comes up a lot is they wish they could get a few solid hours of the manager's time so they can educate them properly on a technology concept.
If you look at leaders as they move up the chain, one mark of who gets to the next level is who has learnt to be "selfish" enough to really leverage the resources under them. People are often under the misapprehension that these leaders are just sociopaths or heartless but if you actually ask them, it's not comfortable for them either and it's something they've had to learn but it's necessary mathematically to get any work done as your span of control increases.