# Design Pattern the Julian way?

**URL:** https://discourse.julialang.org/t/design-pattern-the-julian-way/29002
**Category:** General Usage
**Tags:** design-pattern
**Created:** [September 20, 2019, 2:33pm UTC](https://discourse.julialang.org/t/design-pattern-the-julian-way/29002 "2019-09-20T14:33:54Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [September 20, 2019, 5:31pm UTC](https://discourse.julialang.org/t/design-pattern-the-julian-way/29002/2 "2019-09-20T17:31:41Z")

</div>

> [@atthom](#):
>
> Due to multiple dispatch which is a fundamental difference over OOP, I expect some variations, and maybe some patterns are just not applicable.

In fact, multiple dispatch is so powerful that the usual OO “design patterns” are mostly not needed. Some studies were written about this for Common Lisp/Dylan, and most if it is applicable to Julia (even more so, since Julia’s parametric type system is more advanced in some directions).

See [this well-known presentation by Peter Norvig](http://norvig.com/design-patterns/design-patterns.pdf). There is also a view that design patterns are boilerplate that [reveal flaws in a language](http://wiki.c2.com/?AreDesignPatternsMissingLanguageFeatures).

---

_[View the full topic](https://discourse.julialang.org/t/design-pattern-the-julian-way/29002)._