Like most skills, if you don’t code after a long time you’ll become rusty!
Maybe you previously worked on coding projects at work but moved on to another position that requires you to code a lot less or not at all. Or maybe coding is something you do on the side and it's not compulsory that you code.
If you’re not currently working in a position that requires you to code how do you make sure your skills are kept sharp?
At my work I've moved on to responsibilities that requires a lot less coding. But in my spare time I still work on some projects on the side. I'm also working on building a developer community called inspirezone which keeps me actively working on something.
Top comments (2)
This is something that honestly terrified me at one point. My last few jobs have involved a lot more governance and architecture responsibility, and way less coding than I desired.
I think that as you climb to the ranks of senior developer, it's only natural that you spend less time coding and are expected to put in more time with knowledge management, mentoring, and high-level decisions for the team. Doubly so if you are in a leadership position.
I review the documentation for the two languages I use the most: C# and TypeScript. Generics in TypeScript made me super happy. But it turns out that I didn't miss out on as much knowledge as I feared I had. Even if I have to Google things a little bit more, my problem skills are still there. I mentor developers through Underdog Devs in my spare time, and I feel like guiding others in their coding journey has kept my skills sharp.
Thanks for sharing. Becoming a mentor for developers sounds like a great way to keep active!