RE: translation
Mauro Servienti <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <04a6292f489749f09050ad7f12ef868f@AMSPR03MB114.eurprd03.prod.outlook.com> |
+1, if there is no need for translation stay with the UL Lang, translation is a cost that must be carefully evaluated. We are Italian and we use Italian even if in some cases is really horrible, from a code reading point of view. .m Sent from my Amazing Yellow Lumia, typos are guaranteed ;-) ________________________________ From: Tom Eugelink<mailto:[email protected]> Sent: 12/03/2014 07.09 To: [email protected]<mailto:[email protected]> Subject: [domaindrivendesign] translation I have an interesting discussion going on in my team and could use some ideas. We are writing software for the Dutch healthcare system. Usually software written by Dutch developers uses English identifiers, this make hiring external help much more easy. But if you use DDD and start developing based on a Ubiquitous Language, then that will be in Dutch. Even more so, because a lot of the concepts used in our healthcare system are typical for our healtcare system and are very hard to translate. So I am a proponent of using Dutch identfiers; if the client calls it Squirrel it should be named Squirrel in the software. But this is a hard sell. Are there any other non-english developers with the same problem? And how did you fare? Tom ------------------------------------ Yahoo Groups Links