🤔 How do I stay technically relevant?
The transition from hands-on coding to managing and leading teams can be both exciting and challenging.
We spoke to Rohan Jha, Principal Software Engineering Manager at Microsoft, and here’s what he had to say:
“The fear of losing touch with the technology that once defined your career is real, and it’s something most of us face. However, with some intentional practices, it’s possible to stay engaged and continue contributing to the technical direction of your team while embracing your leadership role.”
We couldn’t agree more—dive into all the insights below for a comprehensive view!
1. Keep learning, but be strategic
Focus on what matters: Instead of trying to learn every new technology that comes out, focus on the ones that are most relevant to your team's work. Identify the core technologies your team is using or planning to adopt and invest time in understanding them deeply.
Leverage learning platforms: Platforms like Coursera, Udemy, or even specialized sites like Pluralsight offer courses that can fit into your busy schedule. Set aside a few hours each week to go through these courses, ensuring you stay current with the latest trends.
2. Pair Programming with your team
Hands-on without the pressure: Pair programming allows you to stay close to the code without the expectation of delivering production-quality work. It’s a great way to understand your team’s challenges, provide mentorship, and stay up-to-date with coding practices.
Bridge the gap: By working closely with developers, you not only maintain your technical edge but also strengthen relationships within the team, fostering a culture of collaboration.
3. Contribute to code reviews
Stay engaged: Code reviews are a critical part of the development process, and as a senior leader, your input can be invaluable. It allows you to see the code being written, understand the architecture decisions being made, and offer guidance based on your experience.
Learn from the team: Code reviews are also an opportunity to learn from your team. They may be implementing patterns or using tools you’re less familiar with, and this is a chance to see them in action.
4. Lead technical discussions & architecture reviews
Guide the ship: Your role as a leader doesn’t mean stepping away from technical decisions. Instead, it should evolve into guiding architectural discussions, helping your team make informed decisions, and ensuring alignment with long-term goals.
Stay curious: Engage in technical discussions not just as a leader, but as a learner. Ask questions, challenge assumptions, and keep your curiosity alive. This keeps you mentally sharp and connected to the technical aspects of your work.
5. Get involved in side projects or open source
Experiment freely: Side projects are a great way to stay hands-on without the pressures of deadlines or deliverables. Whether it's a small app, a new tool, or contributing to open-source projects, this is your playground to experiment and learn.
Community engagement: Engaging in open source & side projects also connects you with a broader community of developers. It’s an opportunity to learn from others, get feedback, and stay at the cutting edge of technology trends.
Last words
Staying technically relevant as a senior engineering leader is not just about keeping up with the latest coding trends; it's about maintaining a balance between leadership and continuous learning. By adopting these practices, you can keep your technical skills sharp, contribute meaningfully to your team, and lead with both confidence and competence. The journey may be challenging, but with intentional effort, it’s entirely possible to stay relevant and continue growing both as a leader and a technologist.
Credits 🙏
Guests- Cheers to our super supportive community member Rohan Jha
Sponsors- Thanks to our sponsors Typo AI - Ship reliable software faster
Loving our content? Consider subscribing & get weekly Bytes right into your inbox👇
Share amongst fellow Engineering Leaders and CTO’s! Your referral empowers & builds our groCTO community.