Don't Repeat Your Domain Knowledge
I often feel that we are not using modules/classes/functions to extract domain knowledge often enough.
In this post, I discussed why we need DRY and when is the best time to do it: https://dsdshcym.github.io/blog/2018/10/26/dont-repeat-your-domain-knowledge/
TL;DR:
- We need DRY because we need to eliminate the duplication of knowledge.
- Both “abstract later” and “abstract early” are bad.
- What we really should do is to look out for our domain knowledge and persist them as part of our code.
Read next ElixirMix Podcast 025 - Rethinking Config with Saša Jurić