Also Ubiquitous Language from DDD (domain-driven design) would help to talk not just within the engineering team, but with other stakeholders as well.

That is very true programmer better talk problem domain most of the time. Solution domain may be needed when one teaches another team member or seeks helps with an implementation. The less modules/classes/methods clutter the domain logic the better. Ideally there would be no translation in-between. After all, even such a harmless pattern/concept as a Factory does not add value to communicating problem domain logic. That is probably something every programmer should just synchronously translate to and from.