Beyond Design Patterns

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, th

[matsu_chara]

let me first propose a different categorization system. Instead of breaking the patterns around "what" the problem is, let's try breaking it around "why" the problem is happening in the first place.