In the last post Beyond Inheritance, we talked about looking past “types” and reasoning about objects differently. The conclusion was that inheritance wasn’t necessary for OOP, and often results in more problems than it solves. Well, let’s go beyond that and explore more of what will come from treating objects as containers of behavior. Let’s look at what this means for various kinds of classes:

In my last post, I talked about revisiting the concept of Design Patterns and questioned how useful it is to “learn” them. The conclusion that I came to was that you are better served by focusing on how objects communicate rather than traditional patterns. Well, that’s not the only “traditional concept” that I think we should move beyond. So, let’s talk about inheritance…

Many people teach design patterns as a fundamental step to Object Oriented Programming. They are so universally seen as important that almost every single conference that I have been to has had at least one talk about them. They are quite often used as interview questions to test a candidate’s OOP knowledge. However, just like inheritance, they are not needed for OOP. And just like inheritance, they are a distraction rather than a foundation. Instead of focusing on patterns, I suggest focusing on learning about abstraction and communication. Why? Let’s talk it out…

I will be speaking several times in the coming months at several conferences in the US and Europe. I hope to see you at one of these events!

Lately I’ve been playing around with some functional languages and concepts. I have found that some of these concepts are directly applicable in the OOP code that I’ve been writing. One of those concepts that I think is worth talking about is the Monad. This is something that every functional developer tries to write a tutorial on, because it’s such a cool but hard to grasp concept. This post is not really going to be a Monad tutorial per se, but more of a post about bringing the general concept to OOP, and what that looks like.

Today we are joined by open source contributor Larry Garfield. Larry introduces us to design patterns through his own unique style: Cooking With Crell. He introduces the concept of Design Patterns, goes through a few basic patterns and closes out with some pretty solid justification for why we should care. Check it out:

The Mediator Pattern is an extremely flexible and useful tool to help decouple your code and provide added flexibility in your applications. We’ll explore the basic concept of a Mediator, some places you’ve used it and some things that you can do to improve upon the basic concept. Check out the video:

Today’s Programming With Anthony video focuses on the concept of Iterators. We’ll look at the abstraction that they represent, how they can be used and some of the benefits of using them. When used correctly, Iterators can lead to very efficient, flexible and clean code. Check out the video:

This week, we’re going to talk about the topic of Dependency Injection in Object oriented code (specifically PHP). You don’t need a fancy container to do it, it’s actually quite simple to do manually! Check out the video:

The brain is a muscle, and as all muscles, it needs regular exercise to keep sharp. Or at least that’s what the old adage says. This is a post that I’ve been meaning to write for a long time now, but never got around to (until now that is). Sparked by a twitter conversation with Mr Grumpy himself (Chris Hartjes), I decided that the time was right for it. So, here’s my method for staying sharp and exercising my brain…