I’m an advocate of “build ton of stuff and pause for learning when faced with recurring problems”. Beginning with nearly 100% practice and naturally moving to learn more theory when it becomes important.
It’s definitely not necessary to know how things work in order to be able to use them. The features and interfaces are poorly designed if it requires the consumer to know about the ugly details.
However once a person is gaining experience it becomes very useful to dive into the fundamentals. That will serve well really quickly when advancing towards seniority.
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’m an advocate of “build ton of stuff and pause for learning when faced with recurring problems”. Beginning with nearly 100% practice and naturally moving to learn more theory when it becomes important.
It’s definitely not necessary to know how things work in order to be able to use them. The features and interfaces are poorly designed if it requires the consumer to know about the ugly details.
However once a person is gaining experience it becomes very useful to dive into the fundamentals. That will serve well really quickly when advancing towards seniority.