Re: Re: translation

The general rule of thumb I use is keep to English except for domain specific terms that don't really translate well (reading code in mixed languages is taxing). For things that are easily and directly translatable do it.

Sent from my iPhone

> On 12 Mar 2014, at 07:29, Freek Paans <[email protected]> wrote:
> 
> Imo, translation adds a lot of noise, which makes discussions with customers and co-workers a lot harder because everybody thinks in another language, which causes focus on translations instead of the concept at hand.
> 
> Also, the translations tend to be done rather poorly, either because there is no good word for the concept in English, or because the dev translated it poorly. Both increase the noise problem even more.
> We tend to stick with dutch for domain concepts and english for technical stuff. It looks a bit silly (KlantRepository) but I think  it's actually quite consistent, because the domain language of technical stuff tends to be in english (repository, controller, adapter, that sort of stuff). Translating that would introduce a similar problem.
> I guess it does make hiring external help harder, but usually understanding the domain is hardest, and I don't know if just translating the words in code is gonna be enough to make them understand. Even if it does, I'm not sure if that's gonna weigh up against the problems above.
> Just my experience..
> 
> -Freek
>