There is absolutely nothing wrong with being a junior developer.
Allow me to clarify a few important points:
- I’m not singling anybody out. When I say “you”, I mean it in the general sense. If what I’m saying happens to apply to you, great. My hope is that it’s a learning opportunity.
- There is absolutely nothing wrong with being a junior developer. Everybody starts somewhere. You have plenty of upward career mobility. =)
- Wherever you are now is the perfect place to start taking the next step. Everybody started somewhere, and everybody has a lot left to learn.
- If you are junior (in years or knowledge), you need self-awareness of that fact, and you need to know your improvement opportunities. A clear understanding of what to learn next is a beautiful thing.
- I stand by this statement 100%: If you don’t understand what’s going on with closures, a whole lot of things that happen in JS will go over your head, and that’s a bad position to be in. It will make you confused. It may be very discouraging. It could cause productivity problems for you and your team.
I don’t look down on junior developers. I used to be one. I was junior for too long, because I didn’t have the mentors and resources that developers have today. I didn’t have anybody pointing out the learning opportunities that I’m pointing out. I am trying to be the mentor I wish I had when I was a junior developer.
And I provide a ton of free resources to help you do just that. I make some strong statements. I have some strong opinions. I’m here to clarify what is important to learn, where potential pitfalls are, etc… because it can be confusing territory without a guide.
I am not the right guide for everybody — and that’s OK. If my writing style makes you feel like I’m talking down to you or belittling you in any way, that’s not my intention, and I don’t want anybody to ever feel that way.
There are a lot of other great educators out there. Find one that is a better fit for you.