If any developer tries to become a good developer according to this article then they are likely to end up working for themselves alone with great satisfaction with their IDE knowledge and 0 extra courses taken. Bad part is, such "great" devs will have problems working on any big valuable project where codebase can never fit to one "know-it-all" developer's head.
Today due to complexity of real projects TEAMS get great things done, not individuals. IT knowledge is a multidimensional space and you can never know everything. As it has already been said below, good dev knows thier strengths (their "strong dimensions") and delegate/learn TO/WITH more experienced colleagues. And that includes asking questions and pointing out to lack of your knowledge.
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 any developer tries to become a good developer according to this article then they are likely to end up working for themselves alone with great satisfaction with their IDE knowledge and 0 extra courses taken. Bad part is, such "great" devs will have problems working on any big valuable project where codebase can never fit to one "know-it-all" developer's head.
Today due to complexity of real projects TEAMS get great things done, not individuals. IT knowledge is a multidimensional space and you can never know everything. As it has already been said below, good dev knows thier strengths (their "strong dimensions") and delegate/learn TO/WITH more experienced colleagues. And that includes asking questions and pointing out to lack of your knowledge.