Preface
Recently, many good colleagues around me change jobs, and they always mention the interview process when chatting. The interviewer asks the source code most often. Many people on the Internet think that the construction of rockets and cannons interviewed by big factories will go in for screwing work. I believe many friends also have this question. Then why do big companies still like to ask the source code?
Personal understanding
The following are purely personal thoughts,
Cruelly said: natural selection of things competes, survival of the fittest, sail against the current, retreat if you don’t advance
-
The general status quo:
At present, many 4-5 years of experience are still doing things in the first and second years. Obviously, I have mastered the things in the first two years. I have been doing cv Dafa later. Just relying on these, I want to change jobs. It is 0. Only then did you discover the gap between yourself and the requirements of major manufacturers, so it does not mean that the longer the age, the major manufacturers often look at whether your technology meets the requirements has nothing to do with the age. -
Excellent role models:
There are a lot of big names that are clear examples. Although some do not have long work experience, the accumulated depth and breadth of their usual skills are amazing. They spend more time thinking and learning, and entering large factories is also stable Yes, such friends believe that they can mix well anywhere, and the number 35 has nothing to do with them -
How to select interviewers:
How to quickly locate a person's level through the interview? Obviously, big companies want more advanced +. The usual business code can't explain anything. At this time, it will start from the following Direction to examine our capabilities
1. A solid foundation:
usually ask some regular basic questions, from shallow to deep to see if our foundation is solid and deep, sometimes some interview questions will be asked for us to do (basic interview questions feel meaningless)
2. Scenario-Project:
Give some business scenarios, or ask questions encountered in the project, to examine our resilience, accumulation of project experience and processing capabilities of complex scenarios. Sometimes it also depends on your overall control of the project and whether you have certain organizational and management capabilities
3. Algorithmic questions:
This is also a common routine for some large companies. If it is a temporary question, sometimes we don't have to write it out completely and run (of course it is the best to have this ability), but to examine you more Is your thinking logic clear
4. Source code:
Algorithms do not have to be asked, but the source code is almost necessary. First of all, reading the source code can reflect us: (1) Love to learn and have the spirit of exploring technology. It will get better and better (3) There are many excellent architectures, design patterns, and thinking logic in the source code. . . So don’t think that the interviewer just asks you about the source code just to install X. In fact, what they want to investigate is to read the source code. These abilities that can bring us are not available in writing business code for 5 years and 10 years.
How to read the source code
-
A certain amount of accumulation:
if you have not even laid the foundation, it is definitely not good to see the source code in order to see the source code, and it will only look confused. -
From simple to complex:
climb slowly before considering running. Slowly our programming thinking will be able to keep up. If you can’t chew, you can search for some good source code analysis articles, follow others to learn step by step, until you are not struggling to read the simple source code, then try what you are interested in. Source code -
Look
at it repeatedly: sometimes the first time you look at the source code, it’s only a rough idea. When you look at it after a while, you will find that it is clearer. Some coups and even projects can be used. Be sure to read more, you will find new things every time. (personal experience) -
How often? :
When we can look at the source code, in the project, we must always be curious, think about how to implement it when using components or libraries, so that we have the motivation to learn to read the source code of others, and use it while looking at the source code. There will be a deeper understanding, which is also the most ideal. Don’t look at the source code for the interview -
Take notes-summary:
I now take notes whether I am learning new things or looking at the source code. I have clever logic, design patterns, and good methods to record. I always think that good memory is not as good as bad writing, and then we often take it out and use it in the project. This is the final effect that the source code should have. The ultimate benefit is definitely ourselves.
to sum up
If you don’t advance, you will retreat, so everyone must be aware of crisis.
It is also until the age of 35, ordinary people write business codes, and role models have deep learning to broaden their horizons and promote management.
This is why everyone says that 35 is the threshold for programmers, and many people can’t get past it. In fact, all walks of life are like this, there will be a barrier. The company will always be short of senior talents. Only in this way can they still shine after the storm. Not eliminated by the company or eliminated by society.
There are roads and diligence as a path in the mountain of books, and there is no end to study the sea. The big factory only uses a certain way-source code to understand your technical depth, learning ability, and future development. Even if you screw in, you are the best screwed. Of course, you will not build a rocket for you. Money asks you to screw the screws, and they are not stupid, so learn more and it won't hurt.
Life is like XX, since you can't resist, then enjoy it.
At last
This article shares some personal views, don’t spray if you don’t like it
I also sorted out a learning material. This material mainly includes Java basics, source code analysis, data structure, jvm, multi-threading, etc. Due to limited space, only a small part of the interview questions are shown below. Friends who need the full version can click a link Jump to receive, link: click here to download for free, get code: CSDN