On the programmer's experience in learning English

Remember Lei June's English debut at the press conference in India? or be teased pronunciation is not allowed, but overall, the programmer can be regarded as a better English level group, because in this industry, English information is the most comprehensive, the most timely, the demand for English materials is the most urgent. So, as for my observations, even the newly-started programmers, in the face of unfamiliar problems, can generally consult English documents and find the information they need. But on the other hand, I also found that the programmers who read English documents often do not look like "read English often" in English. I am here to list some of their own learning experience for your reference.

First, the read document cannot be read-only code.

Read the document read-only code, is the habit of many programmers, but also causes the programmer to read a lot of English materials, the level of English is not a corresponding increase in one of the reasons. Previously in the "programmer" to see the introduction of Reading technology book method of the article, put forward the "first code after the text" method, that is, "first look at the code, do not understand to see the text." This kind of reading method can greatly improve the reading efficiency, but if the technical books only look at the code is enough, but also the text to do? Many times, the code is just the tip of the iceberg, the code behind the thinking and logic is the real play, only written words can be explained, but also only reading words to understand.

For example, the code is x = 5; Sometimes the description is x should is not more than five, sometimes the description is X should be no more than five. Without looking up the dictionary, can you clarify the difference between the two statements-the former is "x must be less than or equal to 5", the latter is "x should be only 5", the meaning is different, the application of methods and occasions are not the same.

Over the years, programmers who have been hoping to translate technical documents have come to me to discuss translation issues and to find out how some sentences should be expressed. At first, I also think that this is the problem of Chinese expression, but gradually found that, in fact, more problems in English reading, so my answer is often: what do you think the author said here? to guide the other side of the original meaning gradually expressed, in fact, this time, the real translation has surfaced.

The most recent example comes from this sentence: But as with any web-based system, atom-based Solutions trade scalability for latency, making atom often inappro Priate for very low-latency notifications. The problem seems to be that it is difficult to translate, except that the backbone of the sentence, before there is a but as ..., and then a making .... But I finally found out that the programmer who has doubts about this sentence actually doesn't understand trade...for ... Use (translated as "atom-based solutions need to weigh latency and sexual extensibility"), if you understand that it is "Sacrifice xx for xx" After the whole sentence is quite good understanding, but also very easy to translate: As with all web-based systems, atom-based solutions for the pursuit of scalability, increased latency, So atom does not usually apply hints that require very low latency.

To solve this problem, the first thing to do is to change the "just look at the code without reading the word" habit, at least to do "read the text, realize that its meaning and code is consistent"; Another effective way is to learn some new knowledge by reading the English language of plain text (such as a detailed explanation of in-depth principles), This method I recommend to many friends, very effective.

Second, pay attention to pronunciation.

I have always heard that the Chinese have studied English for many years, in fact, they are dumb English. I do not know how the situation has changed, but as far as I can see, many programmers read a lot of English materials, will join the English discussion group, also dare to say, but there will be many problems in pronunciation. The word "pronunciation" here is not a clear pronunciation accent, but a pronunciation of some terms.

The term source of computer science is very wide. For example, in the design pattern, there is a pattern called facade, many people often read directly as ' f?kɑ:d, in fact the word is from French, the correct pronunciation is actually f? ' Sɑ:d, such as pseudo-code "pseudo" pseudo, the correct pronunciation is ' su:d???, but I seldom meet programmers to read it right, and many people simply don't pronounce it.

Some people may say that these problems are not important, everyone "will wrong", the conventional, but things are not so simple. Recently I was at a technical gathering and a guest (technical master) read the frame name Chameleon (Chameleon) as a ' t?? Milj?n, and the correct pronunciation is k? ' Milj?n, because there is no text material, many people have listened for a long period to know what he said, some unfamiliar chameleon audience is to the end also did not understand. The Chinese party even so, if there is a chance to participate in foreign exchange, read the wrong cause of the problem is greater.

To solve this problem, there is a very good way, is to study the American University of public classes, Yale, Stanford and other schools of the computer department has released a lot of high-quality public classes, learning some of the fine courses, not only can lay the foundation, but also by the passing of many daily encounter, but can not or read the wrong terminology. For example, I learned from the data type char that the pronunciation is kɑ:, not t?ɑ:.

Third, exercise English expression .

If you recite a word, you may have heard the word "passive word" and "active word", the former refers to the words "you can recognize", the latter refers to the word "active application" when expressing. As far as I can see, most of the English that many programmers have mastered is "passive English"--seeing it, but expressing the same meaning does not necessarily mean it.

There seems to be no problem at ordinary times, but if the information is to be consulted, it will create a major obstacle. Compared to the world of Chinese technical data "no responsibility/not responsible for the spread" of the situation, the quality of English technical data is much higher, Google search data accuracy is far higher than Baidu; however, to be able to successfully apply English materials, need to "actively" input information, describe the problem, this time "passive English" becomes a big problem.

I have met many times this situation: even if the answer is close at hand, enter the correct keyword, Google's first result is the answer, but the programmer is helpless-because he did not know the computer "beep" sound is beep, do not know the search "multi-threaded" data should be used concurrency, Also do not know "dead" is the system halt, "black screen" is blank screens, "(login) Nonstop return" is infinite loop ...

To solve this problem, the best way is to read the material more attentively, remember these statements, on the other hand, when it's okay to browse StackOverflow and other sites, do not because the problem is not related to their own neglect, pay more attention to these problems in the end is what, how to express. This way, when you encounter problems, you can quickly find a possible solution and save time.

Some people say that Chinese-speaking programmers, learning English is a necessity, not only to read, but also to read, will express, it is really difficult. There is some truth to this argument, but at present there is no better solution, learn to read, look for pronunciation, exercise expression, can indeed bring their own benefits. In the long run, to change this situation, we need all the people in the Chinese technical circle to contribute to the quality of the material (original and translation can), if only "no responsibility to paste", neither personally verify, nor tidy format, the overall quality of Chinese technical information will only continue to deteriorate, reverse forcing more people to learn English well.

From Devstore

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

On the programmer's experience in learning English