I recognize there are some other paradigms that avoid some of the pitfalls of OOP. But I think it took off because it's useful. I remember first learning OOP, and my spaghetti code got a lot less spaghetti-like.
Any paradigm that sees widespread use is going to have some great examples, a bunch of competent examples, and a wide range of poor implementations. I don't think that's particular to OOP.
I think it takes experience to understand how to architect larger projects well. You need to write your own larger projects and see what original ideas help the project, and which ideas make it hard to maintain. You need to see other projects that are done poorly, and others that are done well. And learning about other paradigms, such as functional programming, helps as well.
I recognize there are some other paradigms that avoid some of the pitfalls of OOP. But I think it took off because it's useful. I remember first learning OOP, and my spaghetti code got a lot less spaghetti-like.
Any paradigm that sees widespread use is going to have some great examples, a bunch of competent examples, and a wide range of poor implementations. I don't think that's particular to OOP.
I think it takes experience to understand how to architect larger projects well. You need to write your own larger projects and see what original ideas help the project, and which ideas make it hard to maintain. You need to see other projects that are done poorly, and others that are done well. And learning about other paradigms, such as functional programming, helps as well.