I made a note of what to look out for if you want to popularize a language.
Don't blame the language the other person is using. Even considering the time and effort of learning a new language and a new library It is best to recommend it only if the other person's work is better.
When the same thing can be done equally and the other party is not in trouble Don't sell your language. (Which language is better will soon become a religious controversy.)
・ "There is such a language." ・ "Why are you using such a language?" ・ "What makes you happy about that language?" ・ "It's enough to use ***." ・ "Can you do *** in that language?" ・ "It's not a hassle to make it in that language and then remake it in C ++." ・ "I don't want you to write in a language that other members can't read." I get this kind of reaction.
Don't get the opinion that "I don't want you to write in a language that other members can't read." Let's speak carefully.
First of all, only within the range of making your own tool Let's use that language. What's more, the documentation is ready for other members to use when the need arises. Let's create it.
The purpose is to increase the choices, It's not a replacement for traditional languages.
First, let's share the code we wrote. Even if you don't write it, let's prepare an environment where it can be executed.
Then the other members I can't write, but I aim to be able to work. (Let's convey the advantage of using tools made by others) Under such circumstances, we will introduce tools that can conveniently solve the parts that other members may be in trouble with.
Think only so that the other person can enjoy the part that is in trouble. -Make it easy to create graphs regardless of the OS type. There are many needs to automate the creation of graphs.
・ Are there any libraries you want to use?
Using a new language is more labor intensive. Therefore, there is a reason to be skeptical about whether to use it newly. "I want to eliminate the fact that it was useless after using it." "I don't want to look terrible at buggy processing systems / libraries." "I don't like the unmaintained processing system." "I don't like having a lot of grammar to remember." "I don't like the difficulty of finding a function to do what I want to do." "I want to avoid languages whose language specifications change frequently."
It's only natural that those who are introduced to a new language should always be careful. A language that has a reliable library in the field you want to write To choose. Keep in mind that the language will change with the times.
"I don't like the hassle of installing the console and additional libraries." "I don't want to use languages with pitfalls." "When you want to rewrite a program that emphasizes speed. I don't like languages that have to be redone." "I want to use a frequently used library of a frequently used language in that language."
"How do you write *** in that language?" "I don't know where **" When there are two or more users other than yourself in the department It will be easier to spread to some extent.
When an authoritative person introduces the language and library Your understanding of the language will be much better.
There is no language without its disadvantages, What are the disadvantages of that language? How can each disadvantage be reduced? It is important to tell.
It's a good idea to take your time to introduce it.
Postscript · Colleagues often use languages, libraries, and tools that are better than the ones they use. Even one version control tool has switched to a more convenient tool. ・ If the library used by a colleague is very good, you can use it as it is, or write a wrapper and use it. I often learn by rewriting in my favorite language.
Postscript: ・ Throw out the magazine that features the language on your desk. ・ Explanation by university professors and introductions by authorities of academic societies and symposiums (slideshare, etc.) introduce. ・ If there is a person who is highly evaluated in other departments in the company and has a user of that language, tell that to colleagues in the department to which you belong.
Some people talk to the language from the perspective that it has no disadvantages, so don't argue with it. When argued, there are people who are stubborn, so it is important to speak in a way that avoids them well.
Some people think it is unknown or scary. Therefore, in Japanese organizations, there are people who take the initiative in incorporating new things into the world and think about them, and people who create new things with their own ideas are overly braked.
If you don't act to reduce those people's anxieties, it can be ridiculous to be banned from using them under the pressure of "don't make tools in a language you don't understand."
Recommended Posts