I like this kind of rabbit holes. This gives a few interesting information on how forking processes behaves on Linux.

Looks like a good resource for someone who needs to get into IPC mechanisms on UNIX flavors.

Unfortunately seems to subscribe to the 10x programmer myth at least partly while trying to debunk another one... apart from that, it was very insightful, shows well how it's a team sport and how you want people to complete each other. The whole "rockstar developer" thing is a recruitment marketing scheme.

Lots of good advices about processes and organizations. It's nicely points out that friction is not necessarily wrong... if you get something out of it.
Also neat reminder in there that code review are here to complete work which is already socialized somehow. If you can't find reviewers it's a sign of an organizational problem when the work started.

A good reminder that there is not a one size fits all solution in the tech world. Also be skeptical of the silver bullets that "obviously" everyone should use. Project context matters above all.