Post is arguing design patterns rather than OOP vs. non-OOP. OOP can save time, lines of code, and can abstract things out if implemented properly. I know guys

Post is arguing design patterns rather than OOP vs. non-OOP. OOP can save time, lines of code, and can abstract things out if implemented properly. I know guys that take it too far, of course, but done right, it does what I mentioned. It sounds like the author got caught up with folks (like I did a couple decades ago) that over-architected software rather than focusing on building.