Skip to main content
Added small explanation
Source Link
Larme
  • 300
  • 1
  • 10

I'm a developper, and I always use English words for technical stuff, sometimes "francisés": "debugguer".

Coding is done in English, so we have to use English (best example: "for", "if", "while" for the most basic stuff we can do). Plus we can this way have a bigger community to discuss with. In France, for the engineers particular case, we have, in order to get our diploma pass the TOEIC (English test). We may discuss that it's not proper to coding, but also to be able to discuss with foreigners during missions, etc, but still. We may not be good in English, but we most of the time are able to read and understand it.

Legifrance (sample: arrière-guichet is back office) gives new French terms. But they seem sometimes "ugly/weird" (purely subjectif point of view from me and colleagues). Plus, they arrives often a few (if not more) years later. 
So when there is no official translation yet, we use the English term, and we get used to it too. I think that is the bigger reason why we keep using English words and sometimes find the French translation strange (with the off topic discussion in comments of this post, I'll say that even if they are etymologically good and well thought, they stay strange because we used another word for years). For instance, to be validated in a French Dictionary (see also in Académie Française), if I remember well, the word has to be safe bet, I mean, not a phenomenon word that would disappear in a few years. And since in computing, everything appears, evolves quite fast, and may also disappears fast, I understand the reticence of having a French translation too soon.

There is also this Techniques Ingénieur which gives some definitions, but I don't know if they are official or not.

I'm a developper, and I always use English words for technical stuff, sometimes "francisés": "debugguer".

Coding is done in English, so we have to use English (best example: "for", "if", "while" for the most basic stuff we can do). Plus we can this way have a bigger community to discuss with. In France, for the engineers particular case, we have, in order to get our diploma pass the TOEIC (English test). We may discuss that it's not proper to coding, but also to be able to discuss with foreigners during missions, etc, but still. We may not be good in English, but we most of the time are able to read and understand it.

Legifrance (sample: arrière-guichet is back office) gives new French terms. But they seem sometimes "ugly/weird" (purely subjectif point of view from me and colleagues). Plus, they arrives often a few (if not more) years later. So when there is no official translation yet, we use the English term, and we get used to it too.

There is also this Techniques Ingénieur which gives some definitions, but I don't know if they are official or not.

I'm a developper, and I always use English words for technical stuff, sometimes "francisés": "debugguer".

Coding is done in English, so we have to use English (best example: "for", "if", "while" for the most basic stuff we can do). Plus we can this way have a bigger community to discuss with. In France, for the engineers particular case, we have, in order to get our diploma pass the TOEIC (English test). We may discuss that it's not proper to coding, but also to be able to discuss with foreigners during missions, etc, but still. We may not be good in English, but we most of the time are able to read and understand it.

Legifrance (sample: arrière-guichet is back office) gives new French terms. But they seem sometimes "ugly/weird" (purely subjectif point of view from me and colleagues). Plus, they arrives often a few (if not more) years later. 
So when there is no official translation yet, we use the English term, and we get used to it too. I think that is the bigger reason why we keep using English words and sometimes find the French translation strange (with the off topic discussion in comments of this post, I'll say that even if they are etymologically good and well thought, they stay strange because we used another word for years). For instance, to be validated in a French Dictionary (see also in Académie Française), if I remember well, the word has to be safe bet, I mean, not a phenomenon word that would disappear in a few years. And since in computing, everything appears, evolves quite fast, and may also disappears fast, I understand the reticence of having a French translation too soon.

There is also this Techniques Ingénieur which gives some definitions, but I don't know if they are official or not.

Source Link
Larme
  • 300
  • 1
  • 10

I'm a developper, and I always use English words for technical stuff, sometimes "francisés": "debugguer".

Coding is done in English, so we have to use English (best example: "for", "if", "while" for the most basic stuff we can do). Plus we can this way have a bigger community to discuss with. In France, for the engineers particular case, we have, in order to get our diploma pass the TOEIC (English test). We may discuss that it's not proper to coding, but also to be able to discuss with foreigners during missions, etc, but still. We may not be good in English, but we most of the time are able to read and understand it.

Legifrance (sample: arrière-guichet is back office) gives new French terms. But they seem sometimes "ugly/weird" (purely subjectif point of view from me and colleagues). Plus, they arrives often a few (if not more) years later. So when there is no official translation yet, we use the English term, and we get used to it too.

There is also this Techniques Ingénieur which gives some definitions, but I don't know if they are official or not.