> In summary, hermit programmers who only write code for themselves are dead because:
> As they don’t plan, you never know when (or if) they are going to finish a task.
>As they don’t document, their code is not reusable because nobody knows how it works.
>As they don’t test, chances are the code they write is full of bugs.
>As they don’t refactor, the software cannot evolve.
>As they don’t handle infrastructure, their code has only been executed on their machine, and only God knows what will happen when the code runs in production.
>As they don’t have good communication skills, they do not know how to sell what they do to the market, which is why they are always behind the competence.
>As they don’t diversify their skills, powerful AI will take over their workplaces.
What does any of this have to do with being a hermit?
I’d also argue that good communication skills are subjective. For instance people in different regions communicate differently, and some skilled people have disabilities affecting how they communicate. In my view it’s important to be open and accepting towards diverse communication styles. There is no “good skill”, that if you don't posses makes you “always behind the competence”