Simple Blog Project
View Single Post
05-16-2009, 04:09 AM
Join Date: Sep 2007
Don't use objects for the sake of using them, objects are only useful if you understand object oriented design (this takes a long time to grasp well). So here's my question: Why do each of those items need to be in a class? What do you gain by using objects opposed to coding them without?
I have found (though both observance and personal experience) that projects made for the sake of using objects are bad. All they teach is how objects work, which is done fine with small useless programs. The nasty side effect that they give is that you get into the thought process of using objects for anything you can manage to create one for. This is not how good design works, objects should only be used when there is a clear advantage to use them.
What I am saying is that you should learn how OOP works with small applications, read up on object oriented design and then start building a larger application. When you build this larger app, use OOP as a tool opposed to the base of the entire project.
View Public Profile
Send a private message to Village Idiot
Find More Posts by Village Idiot