foreword
I used to say:
No matter what kind of interview it is, if you want to avoid being abused by the interviewer, you have to prepare comprehensively by maxing out the interview questions. Of course, in addition to this, you also need to lay a solid foundation in your daily life, so that no matter how the interviewer digs into a knowledge point, you can handle it well~
But now many brothers don't even have interview opportunities, and the link of memorizing interview questions is directly omitted.
At this time, you have to think about whether your resume has not been updated for a long time. So what should our resume focus on?
About Resume
The first thing to mention in the interview is the resume. The resume is really a very esoteric thing. Why it is esoteric is actually esoteric for people like me: poor education and poor work experience.
Of course, this is also related to the current environment of demand for technology R&D talents, and the above two points will increasingly affect the passability of resumes.
Everyone has an idea of a real thing. This is what a former colleague told me in private. He left the company more than a year before me, and then went to a large factory (a large e-commerce company). He is also in charge of recruitment interviews. Isn't it scary? He himself felt intimidated. Having said so much, what should we do? Don't expect to find a good job if you don't have a good education and work experience? Of course not, in fact, the interview is still the internal strength of the test, and the resume is just a stepping stone. If your internal strength is profound and can be well reflected in the resume, then the resume is really just a resume. You should have noticed that there are two points mentioned above:
- Show your abilities well on your resume
- Deep internal strength
How to reflect the ability well on the resume is actually not a skill that a science and engineering student is good at, so you need to write more, revise and ask for advice, and find more experienced friends to help you take a look. Even if you don’t have such friends, I believe everyone has the ability and channels to get in touch with such people.
In addition, there are many articles on the Internet about the format of the resume. This point will not go into depth. I think it is very important to strengthen everyone’s vigilance. It is to use it, but do not know the technical points that are not in-depth. Do not write on the resume. Generally, one side of the interview in a large company must be the resume side, that is, ask the technical points written in your abbreviation. In short, the resume is not the most critical thing for you to pass the interview, the most critical thing is the second point: internal strength
Inner strength is the so-called knowledge. If the inner strength is not deep, if you want to build a house with a weak foundation, the whole house will collapse.
As for us programmers, when it’s time to make a breakthrough in our internal skills, but you don’t know how to break through, you will always be stuck there. This is the so-called bottleneck. The bottleneck has existed since you entered the industry.
What are the 4 bottlenecks that Android engineers with 3-5 years are most likely to encounter?
1. Shallow understanding of principles
Most of the work is simple UI interface development and third-party SDK integration, and I don’t have a deep understanding of the principle layer and underlying development
2. Narrow technical vision
I have worked in small software companies and outsourcing companies for a long time, and my technical vision is too limited
3. Difficult to raise salary
The salary increase space for junior and intermediate Android positions is limited. Basically, if you want to get more than 15k, you will not be able to get things that do not know the source code layer.
4. Few learning resources
It is very difficult to improve after getting started, relying on the simple business projects that you have come into contact with, to practice those cv techniques repeatedly. Most of the technologies on blogs and books are abstract and scattered, which can be used for reference and guidance, but there is no way to copy them into your own
How to break through the bottleneck
It has been observed that most programmers are in this state. Everyone is confused and looking for a breakthrough. The difference is that some people can break through successfully, and some people have been working for ten years, but they are still stuck in adding, deleting, modifying, and not being able to find out. It cannot be denied that most programmers work very hard, can work overtime, and can find a few technical books to recharge in a limited time. This seems to be standard for programmers. But the result is still:
I worked hard, but I was still mediocre.
What is the reason for this phenomenon?
The efforts of ordinary programmers and excellent programmers are not only reflected in the difference in time invested, but also in the direction of effort, the difficulty of effort, and the density of thinking of effort.
Breakthroughs are not necessarily achieved only through continuous learning
Because for many junior and middle-level Android engineers, if they want to improve their skills, they often have to explore and grow by themselves.
Unstructured learning is inefficient, lengthy and unhelpful. After a long time, it is normal to be discouraged after spending a lot of time and effort and not seeing the desired effect
Therefore, you must find the most suitable way to learn, otherwise you will not only waste time, but also delay your future development.
Hey friend. Finally, share a systematic study material
The secret of Android Framework source code development is of great benefit to the advancement of Android programmers!
Due to the excessive content of the document, in order to avoid affecting everyone's reading experience, only some of the content is shown here with screenshots, and there is a free way to obtain the full version at the end of the article! (At the end of the article, there is also a small benefit of using the ChatGPT robot!! Don’t miss it)
"Android Framework Source Code Development Secret"
This learning manual deeply analyzes the Android system source code, explains in detail the initialization process of the Android framework and the working principle of the main components, and aims to introduce the core concepts and technologies of the Android Framework through examples and cases, so as to help developers better understand the design and development of Android applications.
This manual is suitable for programmers with certain experience in Android application development, hoping to help developers better understand and master this technology through in-depth study of Android Framework.
Chapter 1 System Startup Process Analysis
The complete startup process of the Android system can be divided into three stages: the Linux system layer, the Android system service layer, and the Zygote process model from the perspective of the system level; knowledge points: the first section Android startup
overview
,
the second section init.rc analysis,
the third section Zygote, and
the fourth section Interview questions
Chapter 2 Cross-process Communication IPC Analysis
As a mechanism for Android inter-process communication, Binder can be regarded as a driver. In Android, common inter-process communication such as system class: phone calls, alarm clocks, etc.; self-created: like WebView, video playback, audio playback, large image browsing, etc.
Chapter 3 Handler Source Code Analysis
Section 1 Source Code Analysis
Section 2 Difficult Questions
Section 3 Handler Frequently Asked Interview Questions
Friends in need scan the QR code below to get it! ! ! !
At the same time, a WeChat group chat robot based on chatGPT was built here to answer difficult technical questions for everyone 24 hours a day .
