[ecocentrik]

The article is full of useful observations. The one issue I have is that presenting us with the worst possible management scenario for a new developer and using that to build a separate argument about the misuse of resources before that developer was hired is a little convoluted and even fallacious. The section about hiring and mismanaging the new developer can be removed and restructured as a separate article on the best/worst use cases for new developers.

[nahname]

Do you mean the anecdote about hiring a new developer or the general guidance?

Assuming the anecdote, I thought it was a useful example that I have seen occur too many times. I am also sorry to inform you that the scenario presented was actually quite ideal. In all likelihood, the new developer would be incompetent. At the very least, he/she would have a personality conflict with the team and/or argue with them about why everything they are doing is wrong (which should seem obvious anytime you are working 40+ hours).

[ecocentrik]

Yeah, I'm referring to the anecdote about hiring the new developer and expecting them to immediately contribute to bug fixing a mature project. Forget about any disruptive personality flaws the programer might have (which I agree is probably another factor to consider), I read this anecdote as an avoidable worst case management failure scenario and a potential straw man for his argument. So, maybe a little to negatively ideal to serve as a point of reference for his argument.