Recent interview review and reflection, I hope you can get something from my experience.

I was twenty-one that day, in the prime of my life. I have so many hopes. I want to love, eat, but also in a moment into the sky of the half-dark clouds. Later I learned that life is a slow process of being hammered. As one gets older, one’s hopes fade away and one becomes like a battered cow. But I didn’t foresee that on my 21st birthday. I felt that I could go on forever, that nothing could hit me. — Wang Xiaobo, The Golden Age

I have been working in a company for three years, and I have been looking for a job for two weeks recently. The small company is fine, but the big company has repeatedly failed. Today, when the interviewer asked me if I had any questions to ask him.

I said, what do I lack from the best?

Interviewer: You strike me as a fresh graduate. You have a positive attitude in all aspects and can solve problems quickly. However, your knowledge is fragmented rather than systematic. After you solve a problem, you don’t reflect on the knowledge behind the problem and what can be optimized. Me: yes, I am afraid that my three years of experience is only equivalent to one year’s experience. Interviewer: You already are.

I feel ashamed to say it out loud, but it is also painful to reflect on it. So MAYBE BEFORE, I also avoided thinking, optimized and constructed my own knowledge system, and gradually became mediocre.

If you think about it, I don’t particularly like coding, but it’s my business, I do it for a living, I love it, AND I love the sense of accomplishment that comes from solving a problem. Ashamed to say, are facing Baidu programming.

I stayed in a company, just graduated when I contacted some small programs, then contacted VUE, familiar with VUE, slowly set up the company’s project, skilled use of VUE bucket, three years, I am just a skilled scaffolding. Just to use, without really understanding the implementation process and principles behind it. Like a frog in warm water, it finds itself trying to jump out of the pot when it has been cooked.

Specifically, I failed in the following aspects:

  • ** Lack of basic knowledge: ** Lack of basic knowledge of the network, in-depth questions about HTTP and networking will be dead
  • ** Did not review and summarize the project and derivative: ** for the project I did, I did not think deeply about how to optimize, whether I could achieve a similar plug-in, etc., what is the principle of the plug-in I used, but just wanted to solve the problem quickly and left it alone
  • ** Output code without input: ** always accumulates experience in the project, uses the inertial method to solve the problem, has no initiative to systematically learn, has no input output code, finally is just the repetitive work
  • Avoidance algorithms: My previous attitude was, “Don’t use it, don’t see it, don’t care, don’t touch it,” and I got stuck in the neck

Reflect on their way to school met many outstanding students, are good at induction, summary, and absorption, by analogy. This kind of person is not only in study, even in employment, in various industries are very popular, they learn things quickly, get started quickly. Summarize, repeat, absorb for yourself.

See how, see not good and introspection also.

I hope you can take me as a negative example, do not want to learn when you can think of me, “look at that front end, three years of work like a year, do not learn is his consequences.

In the future, I will sort out some questions I asked in the interview and share them with you. I will also analyze the projects I have done to understand the knowledge points behind the questions. This article is the first one I published in Nuggets.

Finally, I like the “crayon small new” picture ah ~