Due to how much industry adoption it’s gotten & how widely known it is by developers, it definitely is here to stay. Even if another framework eventually comes that takes React’s place as the go-to frontend framework, all the existing codebases will still need someone to maintain them.
What’s interesting is that it seems that a lot of newer popular frameworks are trying to build on top of it (IE Next) or support React components (IE Astro). New developments like this makes me think that even if React isn’t the go-to framework in the future, the React skill set will be easily transferable to whatever is.
The pragmatic engineer blog by Gergely Orosz is great, especially when it comes to topics that are career-related or about the tech industry in general.
One easy tip that I’ve found to be useful is keeping your phone in a separate room when I am ready to go to bed. Not only does the light from our phones affect our circadian rhythm, but I also personally find that I end up using it since it’s right next to me. If you do leave it in another room and you wake up via alarm, you get the added benefit of being less likely to snooze your alarm because you have to physically get out of bed to snooze it (and getting out of bed is half the battle of waking up).
Not fully programming related, but one book that made a massive impact on my abilities as a full stack dev was “Refactoring UI” by Adam Wathan & Steve Schoger.
From my experience, a lot of devs who work in a full stack roles are stronger as backend devs but they have some basic understanding of how to build a frontend in one of the popular frameworks, such as React. If we are working with a good designer this is usually enough, but having a simple mental modal for how to make something look good really goes a long way. The way that this book was written gave me a good grasp of this by explaining it in a way similar to how I’d think about software (as opposed to being more vague and abstract, which a lot of design books aimed at designers tend to be).