> But in real life, when there is a team, you run into the fragile base class [1] constantly and changing that base class causes horrible issues across your cod

> But in real life, when there is a team, you run into the fragile base class [1] constantly and changing that base class causes horrible issues across your code base. And then you start writing unit tests for everything and wait 10 hours for building and deployment, which is a good thing because your employer will need more people to do the work. Or you can't fix a bug without creating other 10 new bugs, which is a good thing because your employer will need you to solve that 10 new bugs. OOP keeps people employed. :)