Last year I wrote an article called The Learning Conundrum which described some of the concerns, frustrations, and fears I (and apparently many others) had in regards to the fast rate of change in our industry. The issue struck such a chord with readers that I followed it up with a presentation at O’Reilly’s Ignite at Fluent event which touched on this. I was happy to have several people thank me for talking about this—it made me feel I wasn’t alone.
I’m not trying to say that things are horrible. To the contrary, I think things are simply more challenging. There are times when I truly wonder if these challenges exist because we’re over-thinking solutions, or are not thinking enough about the actual problem. I’ve seen many cases where new tools are created to tackle problems that have already been seemingly resolved. Or worse, when contributing to or enhancing existing tools would probably have been the better route to take. This makes me wonder how much ego or the “not invented here” mentality comes into play.
Ultimately though, we have to evolve. As professional developers, we have to come to terms that ours is a constantly-changing field which will forever force us towards perpetual learning. The sooner you come to terms with that reality and embrace it, the sooner you’ll be able to create a plan to ensure that you stay relevant. This is even more important as ageism, my generation’s four-letter word, seems to be becoming a pervasive issue.
In my post, I outlined some of the things that I’ve done to keep up-to-date. Re-reading it now, those things are still relevant. I’m not saying it’s simple, but staying in the game and making yourself consistently valuable is definitely possible.