The termination of concurrent programming threads
Everything has a beginning and an end. When we start a new thread, the thread will naturally end. Generally speaking, if the thread finishes executing the run method, or throws an unhandled exception that causes the thread to end prematurely, we all call it the natural termination of the thread. For us, how can we safely terminate our thread by ourselves?
Hot fix introduction
1. Development process
When a project has an emergency bug, the traditional development process is to release a new version and guide users to overwrite the installation. Regardless of the platform review and launch time, the user experience of repeating download and installation at least twice a day is very poor. The emergence of hot fixes perfectly solves this problem. After the user receives the repair package pushed by the server, he repairs it while the project is running. The whole process is completed in a state where the user is unaware, and there is no need to download a relatively large installation package, and the cost is small.
Summarized as two advantages:
- No need to reissue version, high repair efficiency
- No user perception, low cost
2. What can be fixed
- Resource restoration
- Code fix
- so library repair
3. Code repair technology classification
There are currently three main options:
- Dex instrumentation/replacement based on class loading and Dex subcontracting scheme
- Native Hook for underlying replacement
- Install Run for class injection
Due to the variety of customized systems by domestic mobile phone manufacturers, Dex plugging/replacement is the most suitable solution in my opinion.
At last
It is said that three years is a hurdle for programmers, whether they can be promoted or improve their core competitiveness, these few years are very critical.
With the rapid development of technology, from what aspects can we learn to reach the level of senior engineer and finally advance to Android architect/technical expert? I have summarized these 5 big pieces;
I have collected and sorted out the interview questions of Alibaba, Tencent, ByteDance, Huawei, Xiaomi and other companies in the past few years, and sorted out the requirements and technical points of the interview into a large and comprehensive "Android Architect" interview PDF (in fact, more than Expected to spend a lot of energy), including the knowledge context + branch details.
Java language and principles;
big factory, small factory. Android interview first see if you are familiar with the Java language
Advanced UI and custom view;
custom view, the basic skills of Android development.
Performance tuning;
data structure algorithms, design patterns. All of the key foundations and key points need to be skilled.
NDK development;
future direction, high salary is bound to be.
Cutting-edge technology;
componentization, hot upgrade, hot repair, frame design
There are a lot of materials for learning Android on the Internet, but if the knowledge learned is not structured, and when you encounter problems, you just taste it and stop studying it in depth, then it is difficult to achieve real technological improvement. I hope that this systematic technical system will provide you with a direction reference.
When I was building these technical frameworks, I also sorted out the advanced advanced tutorials of the system, which will be much better than my own fragmented learning effect, visible on GitHub; "Android Architecture Video + Study Notes"
Of course, it is not easy to learn and master these abilities in depth. Everyone knows how to learn and what work intensity is as a programmer, but no matter how busy the work is, I have to spare 2 hours a week to study.
Within half a year, you will be able to see the changes!
Everyone knows how to learn and what work intensity is as a programmer, but no matter how busy the work is, I have to spare 2 hours a week to study.
Within half a year, you will be able to see the changes!