One of the more disconcerting things I hear developers say is "I'm a React developer" or "I'm a Meteor developer." This is something I used to say and, as my own skillset has evolved, I've realized the danger in pigeonholing yourself that way.
Now, you may think "Hey, wait a minute! I'm an ___ developer!"
Don't be angry.
The reason I say this isn't to shame or degrade but to share a bit of grey beard wisdom. When you identify as an X tool or X framework developer, you're putting unnecessary limitations on your thinking.
Both React and Meteor rely on functions. Both rely on variables. Both can take advantage of the
Why is this important? Isn't this what 39 year old developers fight over when they're waiting for their coffee?
As my skillset evolved, I started to understand the divide between a framework and a programming language. Gradually, I started to learn that by understanding the underlying language, as a developer, it was easier to adapt to any tool or framework.
And this is the point.
When you focus solely on a framework, you limit the potential to evolve your skillset, or, in the event that your tool of choice is tossed into the recycling bin, the opportunity to transfer your skills to something else.
If you focus on the language, though, and its features (e.g., how Promises work or the difference between a
forEach and a
map), your adaptability increases. Your speed increases, too, because your brain starts to understand the syntactic boundaries between the language and the framework—you start to understand that a
As with anything, of course, this takes practice. But, by paying attention to how you think about your own skillset, you greatly increase your long-term potential and value as a developer.
No spam. Just new tutorials, course announcements, and updates from CheatCode.