<ul>
<li>Do not violate the  <a target="_blank" href="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it">YAGNI</a> principle. You aren't gonna need it.</li>
<li>Do not violate the  <a target="_blank" href="https://en.wikipedia.org/wiki/Principle_of_least_astonishment">POLA</a> principle. Principle of least astonishment.</li>
</ul>
<p>My preferences</p>
<ul>
<li>Domain-Driven Design. </li>
<li>Functional programming.</li>
<li>Test &amp; Behavior Driven Development</li>
<li>Clean Code: A Handbook of Agile Software Craftsmanship by Robert C. Martin.</li>
</ul>
<p>Domain assembly must</p>
<ul>
<li>Only have code defined by the ubiquitous language.</li>
<li>Have pure functions. A function is called a pure function if it always returns the same result for the same argument values and it has no side effects like modifying an argument (or global variable) or outputting something. The only result of calling a pure function is the return value.</li>
<li>Have tests covering all business rules.</li>
</ul>


- Do not violate the  [YAGNI](https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it) principle. You aren't gonna need it.
- Do not violate the  [POLA](https://en.wikipedia.org/wiki/Principle_of_least_astonishment) principle. Principle of least astonishment.

My preferences
- Domain-Driven Design. 
- Functional programming.
- Test & Behavior Driven Development
- Clean Code: A Handbook of Agile Software Craftsmanship by Robert C. Martin.


Domain assembly must
- Only have code defined by the ubiquitous language.
- Have pure functions. A function is called a pure function if it always returns the same result for the same argument values and it has no side effects like modifying an argument (or global variable) or outputting something. The only result of calling a pure function is the return value.
- Have tests covering all business rules.


My software development principles.