@dtetreau
I got the answer to this question when I read "You don't know JS". In my view, understanding the underlying mechanisms and the thought process behind the design of any particular feature in the language is the test of your knowledge. Take any one thing in the language that you think you understand and ask yourself:
What problem does it solve?
What if this feature was not there? How clumsy was the alternative?
(Most important) What compromise does this new feature add? (What benefit did you lose with respect to that clumsy alternative?)
For every important feature in the language that you are able to answer these questions, you develop confidence.
However, remember to not worry when every single thing seems like a rabbit hole. At a later time, you will know where to revisit some of the parts which you can skip for now. When you study something deeply, you will feel you know so little. But that is part of learning. You cannot skip that phase. Enjoy the unending journey into your own ability to reason things!
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.
@dtetreau
I got the answer to this question when I read "You don't know JS". In my view, understanding the underlying mechanisms and the thought process behind the design of any particular feature in the language is the test of your knowledge. Take any one thing in the language that you think you understand and ask yourself:
For every important feature in the language that you are able to answer these questions, you develop confidence.
However, remember to not worry when every single thing seems like a rabbit hole. At a later time, you will know where to revisit some of the parts which you can skip for now. When you study something deeply, you will feel you know so little. But that is part of learning. You cannot skip that phase. Enjoy the unending journey into your own ability to reason things!