"Successful" OOP design pattern implementations are generally dependent on the kind of team you are surrounded by, and the people that maintain the code down the road. If you are, or want to be in a position to influence those decisions, OOP is good to have in the toolkit.
But most devs don't want to be in those positions :) Cause it involves a bit more people wrangling than code wrangling.
But most devs don't want to be in those positions :) Cause it involves a bit more people wrangling than code wrangling.