You are missing the point a bit - I don't think the OP is saying that a bad engineer ("difficult to work with", "don't produce maintainable code", etc) suddenly becomes better when they work by themselves. The point is that one person working alone can sometimes be significantly more productive than if threw more people at the project.
The natural engineering management answer to so many problems is "I need more headcount" - but often that can be the opposite of what the problem needs.
Agreed. I considered referencing The Mythical Man-Month: Essays on Software Engineering by Fred Brooks. The central theme is that "adding manpower to a late software project makes it later". I think that this theory can be applied to both new and late projects. More people does not typically increase productivity.
These guys are usually known as the BBM and are can[sic] appear to be awesome
BBM, aside from the somewhat dated reference Blackberry Messenger, can be a reference to African-Americans, which many (including myself) find offensive.BBM = brilliant bipolar mind
These guys are usually known as the BBM and are can appear to be awesome but by the time you realize their shortcomings ultimately make them impotent and their work irrelevant, it's too late.
I don't care how brilliant you are. If you don't produce maintainable code with well thought interfaces, your brilliant code is going to rot by itself after you are gone. Brilliant and productive programmers also exhibit empathy for other developers who will maintain and extend the code or build other systems to interface with the code written by the alpha coder.