OO works well in some cases. Procedural in some. Functional in some. And a lot of it is how it fits the person. There are different ways of thinking, and a dif

OO works well in some cases. Procedural in some. Functional in some. And a lot of it is how it fits the person. There are different ways of thinking, and a different way matches more naturally to an architecture choice. Some of it fits the problem; sometimes performance is top priority, sometimes it isn't. Sometimes maintaining a consistent architecture for decades across a large team is important sometimes it isn't. Sometimes it's the organization. We've recently switched to Domain Driven Design, I don't naturally tend to like it, but for how our organization and communication is structured, it helps get the business logic into code in a way that didn't exist as well before. Learning about architecture and picking the right tool for the right job is important. OO might never be the right tool for you, but may have more use to someone else.