As mentioned above, either the code works or it doesn’t … but it needs to work in combination with all the code being added to the codebase by your teammates.

As mentioned above, either the code works or it doesn’t … but it needs to work in combination with all the code being added to the codebase by your teammates. That is Linus' job (or one of his trusted lieutenants). Kernel contributors generally do not interact with each other directly. There are simply too many kernel contributors to hold all kinds of "team meetings". The problems that the article mentions, exist mostly in a corporate environment. Virtual, distributed teams generally do not have these problems. Software engineering is probably the most collaborative work in today’s world. Yes, but successful software, such as the linux kernel, is not developed in the way he believes it is. What corporate IT typically does, is certainly not a reference. A manager who doesn’t understand this is a manager who doesn’t understand software engineering. A manager who does not read, evaluate, and merge pull requests, is not a manager; and does indeed not understand software engineering. The article complains about the side effects of one particular, rather outdated approach to software engineering. You will, for example, not hear the PostgreSQL or the Debian team complain about that kind of issues.