The author suggests a common opinion on patterns, that I have seen violated a billion times: > Two people with a common set of patterns find it easier to commu

The author suggests a common opinion on patterns, that I have seen violated a billion times: > Two people with a common set of patterns find it easier to communicate [...] than those without one. > [...] writing down our shared context lowers the barrier to entry. In my experience this is often not the case. Patterns come along with labels and the labels will be put everywhere in a codebase. Assumptions get made and replace discussions, leading to a diluted codebase. For example Repositories will become synonyms for "thing that does database access", and will then be reduced to stupid GetByID wrappers [1]. Even worse, some patterns make entry really hard. I used to work with C# and ASP.NET MVC. There, a view is the thing that contains markup, the thing controlling the input is the controller. Then I started using Flask and was utterly confused, since there the functions with the @app.route decorators, which are run on the server and then return markup rendered via jinja2 templates, are called view functions. In Django this is understanding is the same. I was really baffeled. I could not reapply my understanding of the patterns across these domains. This is just one explicit example that I wrote about in my blog [2], but I really made the general experience that patterns replace or inhibit discussions, rather than improving communication and understanding. [1] http://philcalcado.com/2010/12/23/how-to-write-a-repository/ http://philcalcado.com/2010/12/23/how-to-write-a-repository/ [2] http://www.cessor.de/on-patterns http://www.cessor.de/on-patterns