When interviewing for a job on the front end of the web, what questions will be asked?

Summary. The first is to have content. What is gotta content?

Even when you introduce your previous company, you can't say nothing. You tell the interviewer that my last company was a new **, so it is equal to nothing. The interviewer can tell from the name of the company what exactly this company does.

What he wants to hear is not your general, but to introduce some specific business of the company or your specific work.

If you have to have content, then the interviewer will feel that you were very serious at your previous company. Your serious attitude is very good and can make the interviewer like you very much. If you don't have anything in your stuff, then the interviewer will also think that you are very perfunctory and will give you a lower score in mind.

The web front-end interviewer asks you what you were primarily responsible for in your previous company.

Hello. The first is to have content. What is gotta content?

Even when you introduce your previous company, you can't say nothing. You tell the interviewer that my last company was a new **, so it is equal to nothing. The face of the collapse of the test officer can tell from the name of the company what the company really does.

What he wants to hear is not your general, but to introduce some specific business of the company or state guess that it is your specific job. If you have to have content, then the interviewer will feel that you were very serious in your last company. Your serious attitude is very good and can make the interviewer like you very much.

If you don't have anything in your stuff, then the interviewer will also think that you are very perfunctory and will give you a lower score in mind.

The second is the need to be logical. What is Logic? It's yours, and you need to analyze it from all aspects.

For example, the main operation direction of my last company is live broadcasting, followed by self-media shouting birds, and I am engaged in the so-and-so Liangzao department in the self-** module, doing so-and-so work. And at this time, you can talk about some of the achievements you have made. Your logic should be reasonable and rigorous, you can't talk nonsense at will, you can't say whatever comes to mind, you need to organize the language in your head before you express it to the interviewer.

And it is also important to note that you do not reveal some inside information about your previous company. Sometimes, some of the inside information we learn is top secret information from the previous company. For example, the company is cooperating with a certain company or has received some projects, these are all we need to keep confidential, you only need the general direction, not some specific things.

The third is that it needs to be consistent with your current job, no matter what the situation is, you need to make a connection between your previous company and the company and position you are applying for at the end. If you're working across industries, you're going to talk about some of the experience you had with your previous company, what you brought to you, and how you can apply that experience to your new role. If you are not cross-industry, then you need to emphasize some of the experience and achievements you have gained in the previous company, and tell the interviewer that the experience of the previous company can make you more qualified for the job.

Summary: An interview is actually a test of your emotional intelligence.

1. The relationship between redrawing and rearranging:

Redrawing does not cause reflow, but reflow does cause redrawing, and the reflow of one element usually leads to a series of reactions, or even triggers the reflow and redraw of the entire document, which is costly for performance.

2. The concept of redrawing:

Redraw is a browser action triggered by a change in the appearance of an element, such as changing properties such as visibility, outline, background color, etc. The browser redraws the element based on its new properties, giving it a new look. Due to the browser's flow layout, calculations on the render tree usually only need to be traversed once.

The exception is the table and its internal elements, which can take several calculations to determine the value of its properties in the render tree, which takes twice as long as the equivalent element, which is one of the reasons why we try to avoid using a table to lay out pages.

3. Triggering the rearrangement:

When the page is rendered initially; Browse the Bijin ballast window to change the size; When the size of the element changes; When the position of the element changes; When the content of the element changes; When adding or removing visible DOM elements.

4. Disadvantages of redux:

1) The data required by a component must be passed by the parent component, and cannot be taken directly from the store like in flux.

2) When a component-related data is updated, even if the parent component does not need to use the component, the parent component will still be re-rendered, which may affect the efficiency, or you need to write a complex shouldcomponentupdate for judgment.

5. Understanding of MVC and MVVM:

1) MVC:View sends instructions to the controller After the controller completes the business logic, the model is required to change the state and the model sends new data to the view, and the user gets feedback that all communication is one-way. Angular uses data-binding

The change of view is reflected in the viewmodel since the movement of the shirt, and vice versa. Components: model, view, viewmodel

2) View: UI interface ViewModel: It is an abstraction of View, responsible for the conversion of information between View and Model, and transmits the command of View to Model; model: data access layer

1. IE browser kernel: Trident kernel, also commonly known as IE kernel;

2. Chrome browser kernel: collectively known as Chromium kernel or Chrome kernel, it used to be the WebKit kernel, and now it is the Blink kernel;

3. Firefox browser kernel: Gecko kernel, commonly known as firefox kernel;

4. Safari kernel: WebKit kernel;

5. Opera browser kernel: originally its own presto kernel, later webkit, and now blink kernel;

Browser, cheetah browser kernel: IE+Chrome dual kernel;

7. Sogou, Aoyou, QQ browser kernel: trident (compatibility mode) + webkit (high-speed mode).

8. Browser, Window of the World kernel: IE kernel;

Browser kernel: It used to be IE kernel, and now it is also IE+Chrome dual kernel;

Grasp the different content corresponding to different routes on the front-end, such as vue-router in vue, reactrouter in react, etc. Appears in a single-page application, the public part of the page remains unchanged, and only some of the content is used. When switching routes, different components are dynamically loaded according to different routes, and the page is not refreshed.

Pros:: Realize the separation of front-end and back-end, relieve the pressure on the server, do not need to get it from the server every time, quickly display it to users, and provide a better user experience.

Seen in multi-page applications. Each time Sola sends a request to the background server, the server responds to the request, splices the HTML file in the background and sends it to the front-end for display, returns a different page, and the browser will refresh the page.