This guide although has an impressive list of tech, but I'm missing here the reason behind learning all of that.
IMO the list of tech you worked with doesn't make you a Pro.
What makes you a Pro is knowledge:
why to use this or that tech
general app architecture
why when and how to manage app state
what patterns to use for doing various stuff
being able to quickly grasp the app structure to see the best way to implement a particular feature so that your colleagues don't WTF on reviews.
this only comes with experience and continuous learning.
Lurking in the code, participate in open source projects that you use, etc.
By the way, if I find someone who would claim this stack in their CV and 3 years of experience I'd question the proficiency. It's most likely to be a very shallow knowledge of all that stuff.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This guide although has an impressive list of tech, but I'm missing here the reason behind learning all of that.
IMO the list of tech you worked with doesn't make you a Pro.
What makes you a Pro is knowledge:
this only comes with experience and continuous learning.
Lurking in the code, participate in open source projects that you use, etc.
By the way, if I find someone who would claim this stack in their CV and 3 years of experience I'd question the proficiency. It's most likely to be a very shallow knowledge of all that stuff.