Programmer's struggle history () three-month work summary

Wen/Wen guobing

 

Some netizens often ask me which company I work for. Frankly speaking, my current company is a start-up company with no aura, no show off, and some are steadfast and earnest. That's why I have more opportunities.

 

I haven't updated my article for a long time. In fact, my work is really busy, but I will make sure that I have at least one article every month. In his book "seeing", Chai Jing mentioned Chen Yu's sentence: "Don't forget why you set out because you are too far away 」. Maybe we should stop in a hurry from time to examine ourselves and reflect on ourselves.

 

I have been working for three months, and I have made new gains every day. In the past few months, the best habit has been to write documents. I have accumulated several valuable documents from my work to the present. I think this is an embodiment of experience. There are many excellent documents on gitbook for your reference. I write documents in strict accordance with the requirements, such as the source, directory, layout, text, document information, author information, and so on. Here are some tips. First, the document can adopt the software engineering version idea, and add an Update log before the document to clearly understand what each version has done, in this way, it will be clear to check later. In fact, this is equivalent to the change log in the software. The second technique is to use knowledge management tools for synchronization, such as Evernote, Dropbox, Google Drive, and Baidu online storage. The third technique is to write documents without having to use Word or Wps. You can also use the markdown Editor, online or offline. If you are online, you can use markdownpad for both Mark and offline. Currently, I am actively transferring to markdown.

 

The second one worth mentioning is the data retrieval technique. When you encounter problems, you can quickly locate the problem, quickly seek help, and quickly find the required information. This is your competitiveness. At present, what I admire most about our boss is the ability to search. Maybe this is a key factor. Now, the first consideration is Google, which has basically been deprecated by Baidu. Of course, the benefits of GFW make it difficult to attack the city. A good technique is that you can find reliable methods for any problem. For example, I have tried many tools across Great Wall, and finally switched to the paid camp. Currently, green VPN is used. This is quite reliable. If you need it, try it first, if you think it is not bad, you should pay for it. Believe that payment is reliable. In this period, I have mastered some search skills. Every IT developer should learn how to use the search engine efficiently. I will share some information about this. If you are interested, click here to view details. As an IT practitioner, you should or must use Google.

 

The third thing to talk about is English reading ability. First-hand materials are always in English, so you should know how important English is to you. Don't be afraid to get a manual, and be brave enough to try it. It may be very painful at first, but your English reading ability will eventually reach a qualitative breakthrough with the accumulation of data. For example, now I have no pressure to read an English document. At most, I don't know some technical terms. I can check Google Translate and Wikipedia to find out. Our boss is a returnee, so the English document is a small case for him. This is another place I admire him.

 

Next we will briefly discuss the technical summary. Because it is a start-up company and a self-built data center, I need to do a lot of complicated and trivial work in the early stage, such as moving cabinets, connecting crystal heads, installing switches, and configuring routers, finally, I understand that O & M and DBA are all complicated. In the whole process, I am a hardware idiot who has gained a lot of insights. There are several points worth mentioning about the technology. The first point is never to stick yourself with experience or mindset. Experience is certainly a good thing, but if the environment changes, the previous may no longer apply. For example, if the system on the server is installed, I do not know that many servers still have hardware compatibility problems, or even some Linux distributions cannot run. For example, due to different configurations caused by different Linux releases, the company's master server and other servers use different releases, so many things have to be solved in a new way. The expectation and reality are usually two different things. The best thing is to treat everything as a new thing and treat everything with a sincere and humble heart. The second point is that the configuration service cannot be fully performed according to the document. Even if the environment in that document is exactly the same as that in your environment, you do not need some plug-ins. You should flexibly change the configuration method according to your needs. The third step is to understand the software version used in the document, the environment in which the software is running, and the dependencies and versions between different components before configuration, A large part of the problems can be solved in the later stages. In the implementation process, you must not skip this step. What you skip is perhaps the most critical. You should read it from the initial part of the document, there is really no need to know what it is doing. The fourth point is to think clearly before doing anything, and try to avoid useless work. At this time, mind map can help you well. The fifth point is to avoid repetitive work as much as possible. In this case, the script shows its power. In addition to mastering shell, Python and Ruby are worth your research.

 

At the beginning of work, it is very likely that you are impatient. I always want to solve the problem quickly when I get the task, but it is often counterproductive. In fact, it takes only a small part of the entire task, and how to do it efficiently is the key. I still need time to hone my skills and how to make it more efficient. During this time, I also found my weakness, that is, network knowledge. I need time to complete this part.

 

Next, let's talk about life. The weather in Guangzhou is my favorite. The weather in blue sky and white clouds is very common. I have developed a biological clock. I usually have a rest at around in the evening and get up at around in the morning. Get up early, listen to English, read books, exercise for a while, and then rush to the bus crowd. It is common to work overtime. When I get home at night, I usually spend nine o'clock and have to cook food. So the day is quite tight. However, even if my work is busy, I still don't give up reading and do what I like. From the beginning of the word recognition to the present, there have never been so many books in the year. I often visit the library and can also learn a lot during loose in the library. After work and study, I still keep my exercise habits. I have to play badminton at least once a week, or go to the park to relax. I have to have a good time alone.

 

Finally, I insisted on my opposition to "workaholic 」. I personally think that you should work well during the work, take a good rest during the rest, make good use of the daytime time, improve efficiency, and do other things as much as possible at night. After all, whether it is a revolution or not, the body is capital. Readers may wish to see the "20-mile rule". I believe you will understand it. The road ahead is long. Only by sticking to and maintaining the empty cup mentality can we make better progress and encourage everyone.

 

Good luck!

Robin

October 26, 2014

Programmer's struggle history () three-month work summary