If you want to be an expert in the language yes, you should be able to explain any piece of code, and how does behave at runtime or compiled to.
But most devs do not want to be experts so .. theres that.
IMO, most people likely don't want to be experts because there is a point of diminishing returns after you've acquired a certain proficiency with a language.
That is one reason, there many and all good ones, I did not implied that they should strive to become an expert.
We should have experts to push the boundries further, but just a few is enough
An excellent well-wrapped point. Ground your skillset proficiencies based on the truth that software adapts and will always adapt.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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.
If you want to be an expert in the language yes, you should be able to explain any piece of code, and how does behave at runtime or compiled to.
But most devs do not want to be experts so .. theres that.
IMO, most people likely don't want to be experts because there is a point of diminishing returns after you've acquired a certain proficiency with a language.
That is one reason, there many and all good ones, I did not implied that they should strive to become an expert.
We should have experts to push the boundries further, but just a few is enough
An excellent well-wrapped point. Ground your skillset proficiencies based on the truth that software adapts and will always adapt.