This winter, a nice feel very long. Winter vacation developed a number of learning programs, look at some books, are orderly conduct. During this period, to help some how just started junior partner into the programmer career, and also talk about some old programmer programmer career planning. Heart has some experience, it is still quite feeling. So, fees boss Jin blog account the dust for many years to find out, ready to write something, and share with you.
let's start! There is a small partner small Z asked me, do not know what is appropriate to the programmer, worked for six months, found their own independent problem-solving ability is very weak. By communicate with him, we found a small Z six months in the unit has been in the role of the code porters. Since the unit code quality is better, the small Z can be directly vue desktop code copied to the phone side, and also completed the development of the mobile phone side. At that time, I feel pretty good, so we asked him some knowledge vue. Vue on the v-if, v-show are not clear, vuex do not know, even simple js code do not know what that means. To be honest, I was very shocked. So, I asked what he learned knowledge. He learned java, springboot, echarts, mysql and so on. For a programmer newly recruited staff for six months, in fact, learning quite well. But this time the remote home office, do not use the company code, nor the company's knowledge base as a reference, at home, to promote independent small examples of prototypes and small demo. He almost could not write a little code. This is where he is now worried, the gradual loss of confidence, efficiency and effectiveness is very low, a lot of pressure. Later, we talked for a long time, finally probably know the reason why this happen.
1 porter, not a programmer code
Porter programmers work is not code, but with a creative work. Small Z six months of work, basically all day in the company which just copy this code without understanding why so write the code, do not study the benefits so written, for the code to understand the technology involved, nor to carefully study . Maybe you can start things barely cope with the work, but the latter did not form their own knowledge, so it's hard to become a real programmer.
2, requires sustained effort, toughness is very important
Small Z, the first month in which the newly recruited staff, very seriously. In-house test successfully passed the first stage (at that time a small addition and Z together there is another entry of a small partner, but this little partner does not pass the examination, so that the feeling of complacency, so that he underestimated the programmer jobs). But the work in five or six months later, we begin to relax, not seriously, after inert came out, really feel a little pity. Also hit hard code the problem, not solve carefully, always feel that the company has experts to help him get so little in the later increase. So at this time remote independent office, we found more and more knowledge and technical problems. Here, speaking from personal experience, personally feel when you choose this career direction programmer, I hope you can do to prepare my heart a lasting long-term learning.
3, more difficult, bug and more tired heart
Presumably, this is a novice programmer, often confused and frustrated place. However, I want to say, for the old programmer, this feeling is always there, and even the feeling of distress than novices, no less impressive. So, the point peace of mind, because this situation will accompany your whole career. Many times professional confidence, not someone else praise you brought, but what you give in overcoming one difficulty after another sense of accomplishment. And professional confidence which is very important.
4, how to solve the problems encountered in the code
On this issue, the first point, on-line resources are very rich, for routine problems encountered, the Internet generally have a solution. At this time I am sure the first thought is Baidu. But personal point of view, google feel better. Other technical sites and valuable collection of technical documentation to remember, some of Daniel's blog accumulation of attention, some of the technical community, you can also ask your question. Some knowledge here tend to be more comprehensive and more valuable. The second point, the other side of a small partner can seek help, but remember to go to try to solve their own, come up with your analysis of the situation and thinking points, again others ask (do not run into a problem and asked the others, this has been bother others, will also affect the efficiency of others), so you are thinking about technical analysis point of knowledge can and others say the formation of a good contact. Third, learn more reading, especially basic knowledge of, the book will have a solution. Fourth, some of the techniques involve the use of open source components and frameworks, certified reading other people's source code and documentation, often of great help to solve the problem, another good source of reading, to increase your own knowledge very helpful.
5, to realize the idea of the code often comes from life
In addition to the code means of achieving some functions, you might not have thought at the beginning, you can first use of pseudo-code mode, and the life around them linked to think. I once came across a situation, the team is doing features a visual layout (required node on the canvas, dynamic arrangement, dynamic layout, to achieve this layout algorithm), start by accepting the task of junior partner to the visual component is just familiar with, let he realized layout, his face mask ring, do not know how to start. Later, I gave the example of a life, if you prepare the whole family sitting around a square table for dinner, you sit down, this time to your dad, how can he sit? After your father sit down, find the location too crowded, such as your mother will have to come sit, how to do? This time he seems to understand, then I ask, if the whole family sat around a round table to eat it replaced? This time he suddenly see the light. When the code to solve the problem, in fact, solve the problem of life, often linking the two will also have ideas.
6, how to do the coding efficiency is low
IDE good choice, familiar keyboard shortcuts of your IDE can greatly improve your code speed. In addition to re-code work, choose some small tools, or a small write some scripts to help achieve their own, often more with less. Also learn to practice, practice makes perfect.
7, how to improve their technology
Combat! Combat! Combat! I once met a newbie java programmer, java knowledge related to know some of the many new technologies of dry goods have known. But then later we work together, only to find combat capability is very weak. why? Later learned that he had a very "good" habits of mind technical notes, but is entirely liberal arts students take notes law, even practicing the code book, he is not even in the IDE struck, but an excerpt in the notes. And record notes, East 1 West, there is no technical route.
So how to improve the technology, choose a few good book collated, consult an experienced junior partner, to find a line with their current level of understanding of the technology route, it is very important. This technique is often one step compaction route, it will quickly reshape your body of knowledge. Finally, do not forget or combat.
Last point, the programmer's job is not the whole of your life. Retired and sit, read a book other than the technology is often also important. If you have been caught in technology, sometimes we tend to limit your thinking so that you form around strangeness, this kind of life that is not good.