Things I noticed during the interview - follow up

Although I want to add everything up until the beginning of my current job, in order to continue the content of the previous article, I will insert a recent incident here.

The first is about recording the problems learned. Now I have opened a private project for personal use on github. The code in it will collect some personal research content, such as a simple example of comparing the efficiency of several loops in javascript, or New technologies learned at work, verification of information found, etc.

During the new recruit training, because of a few incidents, I began to doubt my learning efficiency and whether I had time to spare, so I began to write work records every day. During the period when I joined the company, what did I do? One hour is the interval, what did you do every hour, what problems did you encounter during the development process, which helpful online articles were checked, and recorded your own process as much as possible.

But this kind of thing is expensive, right? After more than a month, I started to feel a little tired. Now the time interval of recording is more flexible. According to the situation, sometimes it will only be divided into one area in the afternoon, and the focus will be on the things that have been done. Record it, if one day in the future it is found that the work output of the whole day is less than expected, maybe it will be possible to restore the hourly record in a short period of time? For the convenience of future review, I plan to organize and record the specific implementation results by month in the next few days, excluding those trivial parts of the process.

In addition, it also uses the issue function of the github project to record it when it encounters a topic worth remembering. Afterwards, there are more extended discoveries, and you can choose to supplement the issue or open a new issue. What is worth remembering refers to the new topics learned. Some of them may not be just code, but need explanations in the form of articles. The advantage of recording is that you can refer to them later. After all, it has nothing to do with memory. It's not surprising to use. For example, React, which started recently, is not taught systematically, but is directly connected to the front and back ends and understands the characteristics of the life cycle and so on in the process of testing.

It is worth noting that there are some technologies that I am quite familiar with, especially the parts that others may ask, such as git. Although I dare not say that I remember most of the instructions, it is enough to handle the general situation with what I have at hand. It was only after I answered a question of the same period that I realized that "this knowledge may not be as common as I thought." Based on the reasons that may be used in the future, I wrote down several commonly used command combinations and marked them. Use the situation and the problems that can be solved, and it will be easier to answer if other newcomers have similar questions. On the other hand, you can also refine your own narrative style.

I used to want to be a teacher when I was a child, but now I don’t have that plan anymore, but sharing what I know to make the people around me progress is not limited in form, and it can also make my understanding deeper in the process. A sense of achievement is one of my rewards.