What are your reasons for not using transliteration in the code?

Question

Programming

I have one programmer. Not a bad guy in general, hardworking, obligatory. But with his cockroaches and stubborn to horror. I can’t teach him to use transliteration in the code for the names of variables, classes, etc. So, for example, instead of a simple "backcall" writes "zakaz_obrt_zvonok_otk". Every time I get mad, I try to explain, I give different arguments, I talk about standards, but it's all useless. "I'm so comfortable, I'm so used to it, I don't know English...". Please, give me a list of your arguments, maybe I will find something new in them to convince him :) Thank you!

Answer 1

Deprive him of the bonus for ignoring style guides (so as not to spit on the team).

Answer 2

Submit to English courses

Answer 3

Force several times to refactor the names. And then he will start)

Answer 4

I do not know transliteration and have not seen a course on it, but English can be learned. (Here I'm probably lying dumb, but the programmer is unlikely to know English at all)
I read transliteration much more slowly than English. (and this is true, I read transliteration by syllables, it is easier for me to read unfamiliar Romance languages ​​than transliteration)
There are many standards for transliteration, everyone writes as he wants. English is easier.
The names of keywords and other things in the programming language are in English, and the English names of variables and functions will look more aesthetically pleasing foreach object in list: validate(object) than Runglish.

Answer 5

Let him program in 1C if he does not know English.

Answer 6

The code is written not for the convenience of one developer, but in order to implement business tasks. Refactoring and maintainability of code is a business challenge. The convention is the naming of methods and variables in English, since, as already mentioned above, such names look organic when reading the code. As well as tomorrow, for example, the code can go to the international market and the development will be abroad. A non-Russian-speaking developer will not be able to work with such code.
If a programmer has invented his own style guide and does not want to follow the generally accepted one, he has the right to open his own company and implement his style guide in the team there. Otherwise, in another team, it interferes with the main task of the code - supporting business. That is, he does things that are contrary to his direct duties.
It seems to me that here it is necessary to put the question squarely - no super-competencies should be driven by whims. As a last resort, if the developer is a superhuman, send him to language courses.

Answer 7

these are cockroaches in your head, and some dogmas taken from nowhere.
Well, how much can you rape developers and make them think in English, where tell me GDE says that it is necessary to make the names of variables in English?
if you are a transnational corporation like google there -> then yes, you can explain the use of an "international" language in an "international" team for culture,
but if you live in Russia and develop a product in a Russian-speaking team -> don't torture them, don't make them think in English, let them describe the meanings and ideas in their native language (transliteration), the use of English variables will give you nothing but torment and a decrease in productivity.

Answer 8

Show this "unwanted" code in French or in Japanese / Chinese transliteration, and let him try to figure it out and refactor.
Drive vzashey such unwilling.

Answer 9

A lot of programming languages ​​support the name of variables directly in Unicode - so you can not be shy and write directly order_back_call_otk. There is nothing really terribly wrong with this, as I understand it, this is the case when the code will not go beyond the limits of a purely Russian-speaking company. And Russian letters look even better than transliteration, as for me (hello, 1C).
But there is a nuance. Everyone in the company should write the same way. With the same principles for naming variables. With the same number of spaces/tabs. In general, there are many such micro questions.
Get together, choose the standard for the whole company, if the team leader does not have the authority to do it alone. And be sure to control this at the version control level. Non-standard code should not be committed!

Answer 10

There is a technical option: implement a syntax check in the IDE you use and make it "clean" mandatory. Transliteration will not work, but at the same time reduce the number of typos. Especially relevant for languages ​​with implicit declaration of variables like puff with jaboscript.

Answer 11

1. Let this stubborn person remain an example of a programmer with flaws.
2. Alternatively, buy him ABBYY Lingvo, let him play with the clipboard.

Answer 12

Kod vigladit ochen debil'no, budto ego sms-kami nabirali s mobilnika bez russkogo.