Thanks for your comment!

> OOP makes this coordination often very hard to implement.

Fully agree.

> Any successful software program.

Working on a team of 20+ developers is not easy, you will inevitably run into merge conflicts that are tough to resolve. While the software will work eventually, having a shared codebase definitely makes our life harder and slows the progress down. There’s even a correlation between the number of developers and the speed of progress — sure, 2 developers probably are twice as fast as one. However, 20 developers are probably only 10 times as fast as one.

Microservices make things easier by breaking down the codebase, and effectively reducing the amount of shared mutable code.

> Most scientific papers.

Yes, the paper itself is mutable, but most of the work is being done by the scientists in isolation. They probably are not making changes to the same paper all at the same time. Coordination is only needed when the final paper is being produced from individual notes.

Anyways, let me know if the examples can be improved!