Your question touches on the fact that you can improve as a developer in multiple dimensions. Learning new technologies is certainly valuable, but there are other directions to improve.
Regardless of which direction you are interested in improving on I recommend solving a problem (any problem) using a different solution each time. For example, I write similar chess applications multiple times. With each solution I gain a better understanding of the underlying architecture the solution relies on. I find writing in different languages and using different paradigms super beneficial.
As you increase the number of solution patterns you are familiar with you will realise that most problems have a wide range of viable solutions.
For me personally, the most valuable JS knowledge I have came from a course that focused on SML and Racket; the most valuable React knowledge I have came from building a chess app in Elm.
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.
Your question touches on the fact that you can improve as a developer in multiple dimensions. Learning new technologies is certainly valuable, but there are other directions to improve.
Regardless of which direction you are interested in improving on I recommend solving a problem (any problem) using a different solution each time. For example, I write similar chess applications multiple times. With each solution I gain a better understanding of the underlying architecture the solution relies on. I find writing in different languages and using different paradigms super beneficial.
As you increase the number of solution patterns you are familiar with you will realise that most problems have a wide range of viable solutions.
For me personally, the most valuable JS knowledge I have came from a course that focused on SML and Racket; the most valuable React knowledge I have came from building a chess app in Elm.