How to stay technically relevant as you become more senior

as you get more senior, it feels like the amount of time you spend actually coding shrinks significantly, replaced by more meetings, design reviews, and mentorship. this is great for impact, but i sometimes worry about staying technically sharp and relevant, especially with how fast technology evolves. i try to keep up with engineering blogs, do side projects, and deep-dive into specific technologies when opportunities arise. but when my mentees are talking about the latest front-end framework or a new database feature, sometimes i feel a step behind in the hands-on details. there's a constant tension between strategic architectural thinking and staying grounded in the implementation. what strategies do more senior engineers and architects use to stay technically relevant and avoid becoming obsolete? is it about breadth or depth? is hands-on coding still essential, or are there other ways to maintain technical credibility and knowledge?