Philosophy of Object Oriented Programming and Software Design
Posted on November 1, 2008
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!
Tags: Design, Object-Oriented Programming, philosophy, software
Subscribe to feeds
November 13, 2008
[...] object-oriented philosophy is always beneficial for development…and CSS is no exception. How? I tell you. Object [...]
December 20, 2008
also OOP is a tool used in software design. It is not software design. Therefore one should not strive to be OOP developer but to understand how OOP works in software development.
December 21, 2008
Very well said ‘owen’.
June 24, 2010
Yes…
June 24, 2010
Ok.