As I'm now several years into a career that I never expected I would be in, (but loving every second of it) I've been able to look back at a few key moments that happened very early on and how they shaped who I am as a developer and a tech thinker as a whole.
It's hard to pinpoint certain actions that you take or certain things that you learn that really shape you as a person, but for me, this experience was one of them. And it all boiled down to me typing this question into Google:
It's been many times where one of the developers who I employ comes to me and says "Can I use jQuery for just this one thing?" or "Can I pull in Bootstrap for this one project?" And you know what? Sometimes, that's not always the wrong question to be asking, and sometimes it's the right call to make on the projects we're given. But anytime that is asked of me, I take it as an opportunity to invite my developers to think about why they're asking to use it? Is it an example of lack of skill, or is it truly the best task for the job?
All of this to say...I'm not against frameworks. I think in some cases React, Angular, or Vue all have their merits. The tooling and the ecosystems provided to developers today can make our jobs so much easier, but I invite you the next time you reach for a framework you ask yourself "why am I doing this" instead of just doing what is the most comfortable and beginning to think in this way of "what will also improve my skills as a developer on every single project I work on?". I think when we begin to think that way, is really when our personal (and professional) growth begin to explode.
*(this is not the exact article that I read...but it was something along these lines. I searched and searched for the article, but I haven't been able to find it. I wish I could, and I'm going to keep searching)!