I’ve made a Pattern Decision Tree so you never have to wonder what you’re actually doing.

With this tree, you can determine where your code should go. For small projects, it often doesn't matter that much, but with large projects, it is important that everything is in the right place.

What do you think about this? And do you have any feedback?

The diagram was created with [Mermaid](https://mermaid-js.github.io/mermaid/#/). So you can easily make adjustments on [GitHub](https://github.com/reindert-vetter/pattern-decision-tree/edit/main/readme.md).

https://preview.redd.it/eyiqu9l3n6p81.png?width=1790&format=png&auto=webp&s=20d0d94635fea4d6dc4410c381ff8ae66f92e699

8 thoughts on “I’ve made a Pattern Decision Tree so you never have to wonder what you’re actually doing.”

  1. Does this account for the presenter design pattern?

    e.g. `$payment->present->amount` to yield `$1234.56`.

    And what about the pipeline design pattern?

    Reply
  2. I always worry that I’m guilty of building “Fat Controllers” and that perhaps some of my business logic should be moved up to the model layer.

    Does this help?

    I imagine that 90%+ of traffic goes through the path to http->Controller, no?

    Reply

Leave a Comment