Now, I am no expert in OOP or software design, but here’s a philosophy which might help you make the most of what you know about OOP and software design. I have observed and have read reports that people absorb most information when it’s presented in lists, preferably bulleted. So without any further ramling, I present you my bulleted philosophy of OOP and Software Design.
- It’s not how much and what you know; but what you can do with what you know, which’s important.
- Ability to implement Polymorphism, Inheritance, private, public namespaces, static methods etc is no guarantee you are a good OO developer.
- OOP is useless if you don’t use it to create good software design (architecture).
- Using packages, classes, etc does not guarantee good software design.
- When designing your software, think of it as an electronic device you are designing.
- Sketch out the ‘electronic device’. Label the different components, list their functionalities.
- Stay hungry, stay foolish.
That’s it for today. I hope you are blessed with more knowledge, and the ability to make the best use of them. Adios!
