News Feed

News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Brandon Savage:
Using objects doesn't make an application object oriented
July 16, 2013 @ 12:22:34

In this recent post Brandon Savage suggests that just using objects in your application doesn't mean that it's truly "object oriented development." There's other criteria that need to be met to really fit this description.

Lots of developers understand that object oriented code offers advantages over procedural programming. And so, they begin working on creating objects in their own projects, and eventually feel pretty good about what they've done. After all, if they're using objects, their code must be object oriented, right? Well, not exactly.

He breaks it down into three main points that developers should consider when working with OOP in their apps: splitting responsibilities between classes, being polymorphic and using dependency injection. There's no code samples to back up the concepts here, but it's a decent list to think about. There's plenty of tutorials out there about SOLID development and dependency injection in PHP apps, so you might check some of those out to help with these concepts.

0 comments voice your opinion now!
oop objectoriented development responsibility polymorphic dependencyinjection


blog comments powered by Disqus

Similar Posts

Ken Guest's Blog: Book Review: Learning Facebook Application Development Object Orientated Programming - The beginning

Wojciech Sznapka's Blog: Dynamic LAMP setup for localhost development

SitePoint PHP Blog: Building a Web App With Symfony 2: Development

Matthew Weier O'Phinney's Blog: On Visibility in OOP

Community Events

Don't see your event here?
Let us know!

application conference opinion introduction series podcast php7 interview api project yii2 language symfony community framework laravel example part2 list composer

All content copyright, 2015 :: - Powered by the Solar PHP Framework