Product dependency suggestion #16
Description
Would it be too bold to elevate "good module boundaries and requirements" to its own box, likely centered around "Modeled Domain/Shared language between product/tech?"
{{ message }}
Would it be too bold to elevate "good module boundaries and requirements" to its own box, likely centered around "Modeled Domain/Shared language between product/tech?"