Source: dzone.com
Object Orientation and Fallacies of PerceptionCategory: Software, Data
by Term “Object-Oriented Programming” (OOP) was coined by Alan Kay in 1966 or 1967 while he was at grad school.!
All the OOP goodness still there and I think the real problem is not about using OOP in your software design but rather is a side-effect of applying it wrong or using it in a place where that piece of software is not yet ready to benefit from the true power of OOP.
The point I want to make, is that OOP design and style is for humans first and yes it is also possible to have some speed or accuracy benefits from it in code as well, but that is a secondary goal, the first goal is to have software complexity in-check and make it easier to understand and work with for humans and If you were expecting a speed gain through OOP then you are on the wrong side of the history.
I think one of the reasons that you might be struggling with OOP approaches in code, is that you apply it too early and just as it is mentioned in textbooks.
All the OOP goodness still there and I think the real problem is not about using OOP in your software design but rather is a side-effect of applying it wrong or using it in a place where that piece of software is not yet ready to benefit from the true power of OOP.
The point I want to make, is that OOP design and style is for humans first and yes it is also possible to have some speed or accuracy benefits from it in code as well, but that is a secondary goal, the first goal is to have software complexity in-check and make it easier to understand and work with for humans and If you were expecting a speed gain through OOP then you are on the wrong side of the history.
I think one of the reasons that you might be struggling with OOP approaches in code, is that you apply it too early and just as it is mentioned in textbooks.
Related Articles
Community Partners
DevOps Careers