Ubiquity of language... lost in translation ?
By Jérémie Chassaing on Monday, December 1, 2008, 10:49 - Permalink
I found two collapsing problems :
- You should use the same language between domain experts and development teams (DDD)
- You should use English for naming in your code (Design guidelines)
What if my domain experts don't speak English ?
Comments
Ask microsoft to add support for source code localization to VS2010 and localize domain model for each required language / create domain terms for each of them :-)))
or even more stupid idea create wrapper over your domain model for each specific language :-) I'm not joking., I found this second idea.... somewhere :-))
@T> sure !! But they already did it with VB for excel. What a f***ing mess !
But it's true that it's not always easy for us.. we don't have to define one word but two... and there is a lot of false friends. It's sometime hard to find good words in both languages...
What's your technique for this ?
@Jérémie:
I have same sceptical sight as you... but ...I don't see the problem in single vs. multiple word terms across different languages.
I think, that only real solution is localization support in both - modelling tools and IDE. E.g. you write down name for domain entity in English, then you switch IDE to other language(e.g. Spanish ) and write down a spanish term for this entity. No matter of how many words you need to create appropriate name in spanish or english.
But my question is if it would be worth that extra work even if IDEs would support this approach ;-)