I think I made that transition by taking lots of online courses about the stack I was working with at the time. Back then I would constantly get that feeling "Oh, so that's why we do it like this"...
I would also always ask more experienced developers to explain what they knew about that particular subject, and see if what I had learned was correct.
When you study about the stack you use everyday you get into a positive feedback loop where you get to see tons of real life examples about what you have learned, and have the opportunity to practice using them.
Once you have an understanding about what problems the language and the frameworks you are using are trying to solve, and how they do it, it's really only a matter of transposing and filling the blanks when dealing with something new, so it gets easier down the road :)
Hope it helps!
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.
I think I made that transition by taking lots of online courses about the stack I was working with at the time. Back then I would constantly get that feeling "Oh, so that's why we do it like this"...
I would also always ask more experienced developers to explain what they knew about that particular subject, and see if what I had learned was correct.
When you study about the stack you use everyday you get into a positive feedback loop where you get to see tons of real life examples about what you have learned, and have the opportunity to practice using them.
Once you have an understanding about what problems the language and the frameworks you are using are trying to solve, and how they do it, it's really only a matter of transposing and filling the blanks when dealing with something new, so it gets easier down the road :)
Hope it helps!