Modern frameworks are easy to learn. From zero web experience, they help you get productive in a matter of weeks. But for me, the web remained a mystery until I taught myself the very basics.
3 min read
By Kjetil Svalestuen
December 14, 2019
script-tag, supporting otherwise static HTML and CSS. Some picked it up during the days of JQuery and Ajax, where every client-side problem could be solved with a magical dollar sign. Others were introduced to a world of extensive frameworks and abstractions, attempting to solve every problem of web development.
I belong to the latter group. I was introduced to the web in 2016, during an internship at my University. React had just started getting traction, and my colleagues wanted to build new applications using this library with a fancy web stack.
Current users of the web have high expectations of modern web applications. Frameworks attempt to solve the most challenging problems that emerges when building such apps. In a lot of ways, they succeed in doing so. Modern frameworks are surprisingly easy to learn, and during my internship, they helped me get productive in a matter of weeks.
During my internship, this was not a huge problem. I had become productive and was happily delivering features in production. However, the symptoms became much worse when switching to another project with a slightly different web stack. I had become specialized in my current stack, and could not handle libraries, tools and code other than what I initially had learned to love.
To specialize oneself in a framework is not necessarily a good fundament in a rapidly changing world. Frameworks are fragile. Over the years, they emerge, evolve and disappear, only to be remembered in legacy code. It's okay to learn a framework first. Get productive. But don't forget the fundaments they build upon.