[2] https://web.archive.org/web/20050305143929/http://www.cs.du....
That proof-readers, editors, etc work on it too is inconsequential.
TFA didn't say more than one person can't contribute something or work an artistic project. It said that one or a very few people have the direction and the overall command and vision -- e.g. the opposite of "community process" or "design by committee".
Software can become complete broken by a bad patch.
That is seen the best at security issues. Like someone thinks it is a good idea to add a heartbeat extension to ssl. A basically pointless extension, if you have a novel with a pointless appendix from an editor, basically no one would read the appendix and it does not matter that it is there. But with software it ruins the entire server security completely
It is better to pass on 100 good patches than risking one bad patch