A good approach to avoid that kind of technical debt is domain-driven design (DDD). It helps to express concepts discussed with stakeholders directly into the c

A good approach to avoid that kind of technical debt is domain-driven design (DDD). It helps to express concepts discussed with stakeholders directly into the code base. Thus the chance to make errors when translating the customer language into the technical language of developers is reduced. DDD could be seen as the continuation of requirements engineering, since it bridges the gap between specification and code. Both, the specification and the implementation would use the same ubiquitous language.