Amazingly, when engineers under pressure annihilate architectural constraints as a side-effect of hurriedly patching in new features, this is called having ‘high velocity’. Appallingly, this type of ‘velocity’ is the main measure by which engineering progress is judged in Agile. Agile basically turns software companies into Soviet shoe factories.

This is spot on.

So instead of hiring a few talented engineers, our dear Leaders take advantage of cheap labor pools to hire as many interchangeable mediocrites as possible. In spite of all reason and evidence, they continue to insist that 9 women can make a baby in one month. To them it would be a contradiction to believe otherwise.

Pragmatically, there is also much about the inefficiencies of object-orientation that workplace Marxism has come to love. The fact that object-oriented systems suffer a fundamental lack of modularity goes a long way to justify the collective code ownership.

This is wrong, you can perfectly use functional programming techniques within an OOP framework. That is what I do, I use best of both worlds to develop code that is almost bug free and reliable for years to come.

The reason why OOP seems to fail is because people use it wrong. The models are built the wrong way. They use it as some kind of glorified namespace and object layers that is only 1 dimension deep.