>I've always seen design patterns principally as a way of communicating what you are doing to other programmers who come later. I've seen a big project with he

>I've always seen design patterns principally as a way of communicating what you are doing to other programmers who come later. I've seen a big project with heavy emphasis on patterns, and it was a hell for new programmers. Take a month debugging 50 levels of method calls trough the facades and the framework, just to find code that does the business logic.