[humzashahid98]

Related to this subject is Casey Muratori's video about Conway's law and a possible extension to it. The communication overhead of working in teams, and the fact it's harder to address cross-cutting concerns in them, is a key theme in it.

https://www.youtube.com/watch?v=5IUj1EZwpJY

There is also Descartes' quote about how a work produced by one master is often better than one in which many are involved, because of the unifying vision.

[ozim]

But one master cannot go to the Moon.

It takes coordinated effort of many, many people. The same with making a-bomb, the same with making anything bigger in software.

It’s nice that Linus started kernel and GIT but nowadays he’s not writing much code and most likely he would is not able to review personally each and every PR.

[humzashahid98]

You're right. We also have proverbs like "two heads are better than one" and "standing on the shoulder of giants" so people recognise that both sides are important and have their value.

Right now, I'm working on my own on a personal project attempting to do something a little novel and I appreciate being able to go back and refine my ideas/previous code based on things I learn and additional thinking (even rewriting from scratch), when I'm more likely to face friction (like "stick to the suboptimal approach; it's not that bad") and cause trouble for teammates if I was working with someone else. So the value of working alone speaks more to me currently than the value of working in teams, but they both have their place.