resume

The resume of programmer should not be too showy, markdown is ok, but must highlight your technical highlights, resume is like you date with a favorite girl to introduce yourself, when the three good students do not say, just like you interview advanced front-end, do not write HTML + CSS, also do not write vuejs write Todolist

The company

The company can search on Tianyan, Zhihu and Maimai, look at the senior executives and the working atmosphere

The interview questions

In fact, I am very opposed to the practice of brushing questions. Brushing questions should be the last step in preparing for the interview, not the first step. The first step should be to learn the core hard knowledge

Specific front end test questions can also search a lot, probably these categories

  1. JS based
    1. Little Red Book + ES6 book
    2. Typical interview question: How do you count the top three tags on a web page
  2. JS advanced
    1. Javascript You Don’t Know
    2. Handwritten common source code 3. Promise 4. Throttling anti shake 5
  3. Performance optimization
    1. Classic question: What happens from entering the URL to displaying the page
    2. How to make files load faster (cache, network)
    3. How do I make my code execute faster
  4. engineering
  5. Framework Principles (React)
    1. How the React virtual DOM performs (tree traversal and diff)
    2. React 16/15 virtual DOM structure changes, fiber
    3. React-16 hooks implement the React-16 hooks system
    4. The react principle of the router
    5. React how to implement SSR framework
    6. Ant – Design + ANTD – Pro
    7. Redux Ecology (Redux React-Redux, Redux-Saga DVA, UMI)
  6. Framework Principles (Vue)
    1. Will vUE base use is not valuable
    2. Componentization + element- UI source code
    3. Vue has responsivity, why need virtual DOM
    4. The React virtual DOM differs from the Vue virtual DOM
    5. Vuex VuE-Router principle
  7. Computer Fundamentals
    1. Algorithmic data structure
      1. The list
      2. An array of
      3. The queue
      4. The tree
      5. Greedy dynamic programming
    2. Network Protocol (TCP HTTP)
    3. Compiling principle (AST, CodeGen, VUE compile module)
    4. Design patterns
      1. Like king of glory anchor routine, their experience is not rich, learn a look useless, learn a shock thunder cut, cut by each other
      2. Design patterns require a lot of practice

One minute in the interview, ten years in the audience

Any good learning skills, basic are not valuable, such as Vue todo a todoliist is not valuable, Vue source code and design ideas are valuable

Why learn the source code and underlying principles

  1. Need to interview
  2. Architect senior front-end
    1. Do something more high-end and generic
    2. Componentization, frame
    3. There are plenty of best practices in the framework source code
    4. Vue source code, a lot of engineering, design patterns, code specification best practices
  3. Senior front-end
    1. In addition to being experienced
    2. View more
    3. Solve weird bugs
    4. Architecture design

Deliberate practice

The best way to learn a skill, is deliberately practice, every day play chess village king uncle, must be a bad chess basket, I play king glory every day, is also a diamond dish than martial arts master is not every day to fight can, need to practice, need to specially practice internal force, to play DOta as an example

  1. Task decomposition
    1. Repair knife (10 minutes of positive and negative repair in the middle without equipment)
    2. equipment
    3. A hero is tie-in
    4. Pawn line
    5. Hand speed 2. Practice
    6. It’s boring, it’s not fun to repair the knife
    7. Complete practice
  2. Feedback 4 master source (VUejS source code) 5 master comments

Source code learning method

I think there are three levels of source learning. 0. Follow package.json’s NPM run build logic to find the entry point for vue execution

  1. Look at the overall structure, like fold all the functions together and look at the overall logic
  2. Refer to the test code, the input and output of each specific function should be clear, see the logic
  3. Write the core logic by hand (virtual DOM, compile, reactive, etc.)
  4. Group set flag to share, brag force once

How to describe your technical highlights

  1. Star projects I’ve done
  2. Project technology stack and details
  3. The depth of the source
  4. Optimization, performance, experience, geeky
  5. Fill in the pit
  6. growth

How to talk about money

Salaries are flexible when hiring

What we negotiate is pure profit

  1. Know yourself (market)
  2. This advantage
  3. All we negotiated was pure profit
  4. Hr details (attendance, subsidy, 996, five insurances and one housing fund, subsidy

Is known to all

If the truth is understood, I am not very good at learning chicken soup for the soul, but I can refer to these two steps to improve their learning enthusiasm

  1. Check your bank card balance and room rates around you
  2. Boss direct hire or pull check, search the front end, filter salary 30K~50K, see the number of high-paying jobs and requirements

Most of the students read the power, if a lot of nouns in the article you are not very understand, I hope we can use the Chinese New Year this period of time, with vuejs source code to improve themselves, after three gold silver four, the interview to eat chicken

In the future, I will also write special articles on some of the above topics