# "Design patterns of 1972", by MJD

**URL:** <https://www.ruby-forum.com/t/design-patterns-of-1972-by-mjd/68583>\
**Category:** Ruby\
**Created:** [September 13, 2006, 7:25pm UTC](https://www.ruby-forum.com/t/design-patterns-of-1972-by-mjd/68583 "2006-09-13T19:25:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![iceburgh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/c4cdca/32.png) [@iceburgh](https://www.ruby-forum.com/u/iceburgh)\
**Post date:** [September 13, 2006, 7:25pm UTC](https://www.ruby-forum.com/t/design-patterns-of-1972-by-mjd/68583/1 "2006-09-13T19:25:57Z")

</div>

In “Design patterns of 1972”, Mark-Jason Dominus says:

> Patterns are signs of weakness in programming languages.
> 
> When we identify and document one, that should not be the  
> end of the story. Rather, we should have the long-term  
> goal of trying to understand how to improve the language  
> so that the pattern becomes invisible or unnecessary.

Interesting read and quite relevant to Ruby and Rails…

[http://newbabe.pobox.com/~mjd/blog/2006/09/11/#design-patterns](http://newbabe.pobox.com/~mjd/blog/2006/09/11/#design-patterns)

## -r

[http://www.cfcl.com/rdm](http://www.cfcl.com/rdm) Rich M.  
[http://www.cfcl.com/rdm/resume](http://www.cfcl.com/rdm/resume) removed\_email\_address@domain.invalid  
[http://www.cfcl.com/rdm/weblog](http://www.cfcl.com/rdm/weblog) +1 650-873-7841

Technical editing and writing, programming, and web development