Great oaks rise from the earth

The basics are an important step for everyone. No matter what field you are doing, the required courses in computer science must be learned well. In terms of the front end, OS, data structure and algorithm, network these several pieces of content must be mastered, these foundations are not solid, your ceiling is bound to be not high. But in fact, in the process of interview, I found that whether the social recruitment or the school recruitment, basically the foundation is not good. I think, for the school enrollment, the foundation is not good basic and dachang insulation; For social recruitment, even if you have a poor foundation, you can still work, but if the ceiling is not high, your skills will become lower and lower with age, and you will basically stay in the second or third tier companies.

So anyone who wants to go further down the technology path should study computer science. If you are out of school and your English is ok, I highly recommend THE CS61 series. If you can complete these three courses, you will have most of the undergraduate level.

After computer fundamentals, let’s talk about the fundamentals of the front end. In the interview process, I found that most people can ask basic knowledge points or say, but only know. Few people can answer the deeper questions of how to connect multiple knowledge points in series or knowledge points.

For example, cross-domain is a bad question that everyone can answer. This is also a question I often ask, of course, I will also ask a few questions. For example, why should browsers introduce cross-domain mechanisms? Whether the cross-domain request is properly sent and received; Do you understand cross-domain precheck? For the above three questions, there are not many people who can answer them. Most people just know how to solve cross-domain, but they don’t know much about why there should be cross-domain. This also reflects the fact that most people do not have the consciousness to dig deeply into knowledge, but just stay on the surface.

As for the basics, I think we should all reinforce them. If you are a career changer, you should first learn the front-end fundamentals well, and then fill in the computer fundamentals in your spare time. If you are a class, the first is to learn the computer foundation, and then is the front of the foundation, so that you can stand tall, grow fast.

The framework

Frameworks are now a topic that the front end can’t get away from. Many people will tangle with which frame I should choose or which frame is awesome and so on. First of all, before learning the frame, I think you should lay a good foundation first, rather than aiming too high to use the frame first. Moreover, the underlying ideas of the most popular frameworks are the same, and there is no difference between them.

In the interview process, the principle of framing is actually the subject that cannot be avoided. But to be honest, the results of the interview are that few people are familiar with the principle of framework, just know how to use the framework. This is actually a bad phenomenon. For example, when a machine is built, it can be used by assembly line workers through instructions. Even if a group of workers leave, you can recruit another group. But for people who can repair machines or build machines, jobs are easy to find because they are core skills. The same is true for programming. People who simply use apis are not scarce, but intermediate developers at best. However, if you are familiar with the underlying principles of the API, you may be able to move up the ladder to senior development and improve your core competencies. And once you are familiar with the underlying principles, your vision will be higher than others, and you won’t have to worry about what framework to choose and whether your experience will greatly affect your job search.

Therefore, what I want to say here is that it is basic to learn a thing and skillfully use it. After skillfully using it, we should turn to learning its underlying principle and mechanism, or even realize a similar thing by ourselves. When you do this, you never have to worry about losing out, because you’re already ahead of all the people who only use the API, which is definitely the most.

Finally, for everyone who wants to get a good result in an interview, they should do the following:

  • Ramming their own foundation, the foundation determines the height of the building
  • Have the idea of digging deep knowledge, for each knowledge point should consider how to achieve this thing, why to have this thing
  • Don’t be a framework API master, try to understand the underlying framework mechanism

If you can do all of those things, you’re almost 90 percent ahead of the pack, and the road has been shown to you. It’s up to you to go.

Comment section anyway there is nothing to say, all kinds of not carefully read the article began to jump out spray

  1. I interviewed a lot of people with 3 years of experience and only know how to use API. For those who want to continue to improve, shouldn’t they learn more about the underlying things?
  2. Don’t look like the original ideal is very difficult, more to understand the environment of the school now, did not write much code began to ask the framework principle, don’t look at someone else’s salary seems higher than you recruit, it is because someone else is better than you cow force. Don’t underestimate others and overestimate yourself.
  3. Again, read the article carefully. I started with a mock interview. People spend money, and I give them advice, of course, in good places.