I was recently looking into the details of some formal object-oriented programming best practices, and the thought struck me (and not for the first time), "this is way too complicated for the real world."
It isn't that I could not understand the best practices, or that I think the average developer cannot understand them, the issue is that there are so many of these "practices and patterns" (and it feels like they are growing constantly) that I have a hard time imagining that many developers have the patience and the time to not just learn them, but internalize them. The more I look at stuff like this, the more I come to the conclusion that object-oriented programming is not a good way to write software for most developers.
J.JaKeep your engineering skills up to date by signing up for TechRepublic's free Software Engineer newsletter, delivered each Tuesday.
Justin James is an OutSystems MVP, architect, and developer with expertise in SaaS applications and enterprise applications.