My name is Lory, I am a front-end developer. I have been engaged in front-end development for three years since I graduated in 2018. The article will not involve specific interview questions, mostly for their own growth of thinking and reflection, I hope to take this opportunity to help more people, in the front of this road to stick down.

In 2018, I graduated from Zhuzhuerben Non-computer Major. During the interview in 2021, I got offers from Didi, Meituan, Kuaishou, Baidu, Tencent and other companies. In the past two and half years, I worked in a small company and had a bright future. Now that I’m in goose Factory, I’m going to share with you how to stay on the front end.

review

Growing up is never easy.

The first year,

In the lines of the first year knows that his lack of expertise, in complete the job at the same time, the systematic learning the basic knowledge of JS, watched many nuggets on articles in the meantime, summarizes unceasingly, form their own knowledge system, thank you very much here 冴 feather teachers share high quality articles, I have laid a good foundation of JS.

In the second year

After a year of work and study, trying to find a new job opportunities, in throwing more than 30 resumes after the gathering, resume the unexpected is good future home, so has been the only one interview opportunity, I’m excited for this one night didn’t sleep ha ha ha, after five rounds of interview, joined the good success in the future, officially opened the front career, During the period of good future, I grew fastest and took on more things actively:

  • The component library is set up
  • Try tools to solve development process problems (vue-CLI plug-in, Git-hooks application, optimize Webpack configuration)
  • Performance optimization
  • Based on the qiankun landing micro front end
  • Be responsible for daily development of medium and large projects

I really appreciate the opportunity to do a lot of interesting things. I have to say that the future will probably be the happiest and happiest team I have ever worked in.

In the third year

When the education industry is on the decline, I choose to look at new opportunities outside. After about a month of interview time, I got many offers from large factories and many domestic factories. Now I am moving bricks in goose Factory, if you want to see new opportunities, please contact me, so that you can experience nanny-style internal promotion service!

thinking

I believe that there are many people like me, with low academic background and weak professional knowledge, who have experienced endless confusion and confusion after graduation. Here I want to share my learning methods with you through my growth experience, hoping to help you:

Systematic learning

Personally, I think the front-end knowledge is too much and complicated, so I must form my own knowledge system and systematically learn the front-end knowledge. Before, I saw a feishu document shared by someone who saw byte, and I made more expansion and summary on this basis. I also welcome everyone to build together and continuously improve the knowledge system.

During the interview, I also reviewed according to this system.

Reject tool people, think proactively, and try to use tools to solve practical problems

At the beginning of development, it is inevitable to write some unreasonable code. At this time, we can think about how to use design patterns to optimize our code, such as: policy patterns, state patterns, publish-subscribe patterns, etc. These design patterns are easy to find application scenarios in the project.

As the business grows and people expand, there will inevitably be some problems with engineering collaboration. In this case, we can start with the simplest optimizations, such as Git-hooks, webpack optimizations to improve the efficiency of development collaboration.

I think most of the problems in development collaboration can be found on the Github/XX team blog. After all, there are some problems that everyone will step on once. As long as we take the initiative to explore and practice, ** I think this process can be a lot of harvest.

Stand more in the user’s point of view, think more about business

As the front end, I think it is the closest role to users. When we participate in interaction/requirement review, we should think from the perspective of users, what will be brought to users when we make a requirement/function, whether the interaction design/function design is reasonable, whether the requirement document meets the specification, and whether it can bring value to users. Such as:

  • Why is the product documentation always ambiguous
  • XXX received a lot of teasing after it was made (MD, very difficult to use)
  • Why does the page load so slowly
  • .

In my opinion, if we encounter the above situations, as the development students, we have the obligation and responsibility to help everyone to do a good job in the product, the process of standardization, not only limited to the completion of the work, while solving similar problems, their communication skills, product thinking, coordination ability will be rapidly improved.

Below is some of my understanding, just for reference oh

Read more write more Keep loving keep summarizing

Touch 🐟 time can look at Github, nuggets, etc., pay more attention to some big guys, see what big guys are studying, big guys are how to write code, we can start from imitation, step by step, one day we can write good code (mutual encourage)!!

Another point I want to share with you is that we can summarize/reflect on ourselves periodically and learn from excellent colleagues around us.

See how, see not good and introspection also

But we also have to reject PUA!! Never deny yourself because of a performance review/what others say, everyone is the best!

The interview experience

resume

Don’t make a statement. Show value

Bad

Complete XXX functions using XXX components

Better

XXX was used to solve the XXX problem and bring about the improvement of XXXX.

We want to reflect what we bring to the project, not the statement to do XXX function, to reflect their own highlights.

Familiarize yourself with the skills/projects on your resume

Remember not to write something unfamiliar to yourself, it will be very embarrassing to be asked. (Don’t ask me how I know)

The content on your resume must shine! This depends on the usual days and months.

Systematic review

I spent about three months reviewing front-end knowledge, networks and learning algorithms. Must have a system, rhythm, have a goal to review.

In a push fly book document!! yyds

Learning algorithm

I started to learn this part in March. I did 100 questions in three months, and I could write out all the algorithm questions in the interview. (Front-end algorithm is easy)

The first day I did it, I thought I was an idiot…

My method is to classify and summarize the algorithm problems according to different problem-solving ideas, and then keep practicing.

This section is highly recommended for Labuladong’s blog!! I learned the algorithm entirely from the big guy’s articles.

The last

The above are my personal ideas, if there is a wrong place, welcome you to criticize ！！！！！

You can also add my VX exchange: Chen964385822. I just came to Beijing to work for myself! Today is also for you!