I love keeping up with the latest technologies. In fact, I built a site called DevNews a few years ago in which I still use today for finding new tech and software related articles and products.
However, there is a big difference between reading up about a new framework versus actually investing time to learning and potentially even migrating your current code over to it. A lot of the time, it’s not worth it because that framework becomes obsolete or even non-existent in a few years.
I’ve been bitten by this problem many times in the past, and the best advice that I can give is to simply be patient.
For any big projects that you expect to stay around for at least 5 years, you probably want to observe a framework’s community long enough before making the decision to learn and use it. Consider the time that you put in to learning a specific framework or tool to be an investment. That return on investment should be a positive one.
Do you remember Angular? Many developers were using it around 5 years ago, and it was deemed the go-to framework for making a dynamic website or entire web app. It was even backed by Google, so what could go wrong?
Angular 2 was announced and it was completely different from the first version. In fact, backwards compatibility was not even a consideration. Thus the usage of React, a competing option from Facebook, grew.
I personally worked on an Angular project, but I never invested into it deeply. I was skeptical and continued to build my own projects the traditional way (a monolithic Laravel backend with a jQuery and Bootstrap frontend). Fast forward and I am now building multiple React apps.
I believe that this is the correct approach. Use the tools and technologies that work well for you until you know for sure that there is a better way.
Cool cool… but how do I know when there is a better way?
— Avid newsletter reader
Ah, I’m glad you asked. I did an entire podcast episode about this topic! While I talk about React specifically, the principles (community, efficiency, and longevity) apply to any framework or tool. Recommend you check it out 👇
I also appreciate any feedback you might have on the podcast, so feel free to reply back.
It’s still good to be aware of what’s new, especially with small single-purpose libraries. Here are a few articles that I found interesting this week:
Here are my favorites episodes from the podcasts I listen to every week.
This edition of the newsletter is an early exclusive of an article that I will later be publishing to my website, DEV profile and Medium. I would love any feedback that you might have, so my email and DMs are open to you.
See you next Sunday!