I am on both and for some reason, I am enjoying this community more. Maybe UX including interactions with the platform developers as well as members.

Over the past few years I have found inspiration in Michael Hartl’s view on technical sophistication being the new literacy. He created learn enough which I use as a reference for my friends who ask me about what skills they should learn and how.

I feel that it is a needless title as well. However I do realize that for some the term junior dev sparks feelings akin to an indigenous Americans feelings about the Washington Redskins.

I feel early career and jr are both fairly pedantic. If you want to make a distinction I personally think Developer I, Developer II, Developer III makes more sense, but that's me. I have been told also by quite a few people to never call myself junior anything or accept any of those positions and to me that does make some sense. A colleague of mine about the same skill level his first paid gig was entitled Senior Cloud Engineer, and I was being billed as DevOps Engineering Consultant. That being said I wouldn't want someone to look at me and say on you have less than this amount of experience in years and then try to call me junior instead of respecting the years of yard work I put in teaching myself while I starved as a freelancer or the two bootcamps that I put myself through during that time period. And on the flip side of what has been said I don't think I would really want to work with someone who insisted on calling a person something they weren't comfortable with so I think we can agree that the argument goes both ways depending on your background and life experiences. Here is an article that explains some of the mindset behind this point of view which is ironically written by a VP of Tech at Pivotal where my first gig was helping build their PEZ Portal, so I can really appreciate what is talking about. (https://builttoadapt.io/@jmckenty)

This seems to be a decent list of resources. https://www.gatsbyjs.org/docs/awesome-gatsby/

You may think about using Yarn instead as it installs packages in parallel instead of sequentially like npm which makes it noticeably faster on most installs.

I find the community to be excellent.

Katacoda.com, Painless Docker book, Docker Deep Dive by Nigel Poulton, The DevOps Toolkit books, and Linux Academy are great resources that I have personally consumed that were definitely worth the time and cost.

Kubernetes even if only for the job security and solid paycheck. But besides those two points it is an extremely robust orchestration tool and the community that formed around it is one of the largest and dedicated OSS communities out there at the moment.

This video isn't too bad and I will try to find you some more resources as well. https://www.youtube.com/watch?v=8t0vNu2fCCM I would say to dive right in and if you get stuck create an issue on GitHub or jump into the Discord chat room. I recently had a pull request merged into the starter site library so I became a maintainer for Gatsby on GitHub and the community is really amazing thus far. I think the great thing about Gatsby is that you can start out not knowing even very much about React and slowly build up your knowledge as it can get almost as complicated as you want it when you're ready but it doesn't have to be extremely difficult especially to build a simple blog site as was suggested. I will try to find some more solid resources and hope to see you around the community soon. I forgot to mention that Gatsby also offers free pair programming sessions with their developers as well and that can definitely help you learn.