Android is not cool, it's just harder to mix than before
Seven years ago, Android suddenly emerged and became a new trillion-level market. Numerous Nuggets poured in, hoping to show their fists.
At that time, in the mobile gaming circle in the big environment, as long as you had a runable Lianliankan, you could find a job. The industry was pushed forward by the tide.
2020 is coming, the wave speed has slowed down, and the message of bad Android is flying all over the sky. "Cool" is the most common word.
But rest assured, Android is really cool!
Getting started with Android is relatively simple. There are many and many elementary Androids, which are approaching saturation. You can open a recruitment app at will to judge it intuitively. Now Android access conditions are getting higher and higher.
When the standards of an industry are getting higher and higher and the basic things more and more stable, this is not called cold or mature.
text
The JVM language has to put its own status into consideration, considering both its own ability and historical progress.
Java is a pro-son and the "indigenous people" of the JVM, leading the development direction of the JVM. The tree has deep roots and luxuriant branches. "This honesty cannot compete with each other."
Compared with other JVM languages, Kotlin is able to put itself in a more upright position. It does not have the ambition of "the princes will have a kindness" and replace it with Java. Instead, it always insists on the strong compatibility with Java. Use the Java API extensively, wrap the bloated Java code into short sentences, silently doing the work of the "paper maker". So far, Kotlin is quite capable of this role, type inference, expansion, null safety, higher-order functions , which is not practical and powerful syntax enhancement?
In my opinion, the biggest change in Kotlin for Java developers is not to reduce the time wasted on writing code, but a series of changes in thinking:
- Rather than let the developer manually control the loop, it is better to encapsulate the loop inside the class library . The three-stage for loop and while loop of the C-like language are simply the culprits of bugs and complex code;
- Object-oriented, but can't be tied up by classes and objects, liberating functions!
- Every line of code must be used on the cutting edge, to minimize template code and redundant declarations;
- The programming language should design the "default configuration" and guide developers to use the "default configuration" , such as the default class is not inheritable, the access control symbol defaults to public, the collection defaults to read-only, the type defaults to not null, etc.
- ** Immutable objects are better than mutable objects, ** use more val and less var, more read-only collections less mutable collections, more non-null types and less nullable types;
- **Classes should "return to their heart" and only undertake the functions of "abstract objects". **Kotlin encourages the use of extensions, less stuffing APIs and implementations in classes, and try to use "class basic framework + external extension function" Pattern.
These things are implicitly communicated to developers in the process of learning Kotlin and writing Kotlin, and can guide traditional and conservative Java developers to embrace modern programming languages.
Kotlin is not a science, but a set of tools . Unlike Scala, it is not as heavy as a book, and all features are born for practicality and simplicity;
Kotlin is not a revolutionist, but a reformer . It is not Go. It has no ambition to take the world and replace it. It only has a solid goal of "making Java easier to use".
Kotlin is not perfect, but it is constantly improving . Unlike Java, which is controlled by the Oracle family, it does not allow any uncontrolled features to appear. The birth and development of Kotlin cannot be separated from the promotion of the community. More and more new features are being developed. Urged to join in;
Kotlin will not cover everything, but will make up for the shortcomings of Java . Kotlin will not become C++.
The author switched from Java development to Android development in 2013. He has been in a small factory, and he has also been to a large factory such as Huawei and OPPO. In April of 2018, he joined Ali until now.
I have participated in many interviews and interviewed many people as an interviewer. I know that most junior and mid-level Android engineers want to improve their skills. They often grow up on their own. The unsystematic learning effect is inefficient and long, and it is easy to encounter the ceiling technology stagnation!
I have compiled a list of the most systematic Android development mainstream technologies at the Ali P7 level, which is especially suitable for in-depth learning and improvement of small partners with more than 3-5 years of experience.
Mainly include Ali, and the mainstream architecture technology of ByteDance, Tencent, Huawei, Xiaomi, and other first-line Internet companies. If you want to learn Android development in depth and become a qualified senior engineer, you can bookmark these advanced Android technology selections
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 Xmind (in fact, it is better 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 kind of work intensity is as a programmer, but no matter how busy the work is, I still have to spare 2 hours a week to study.
)**
Of course, it is not easy to learn and master these abilities in depth. Everyone knows how to learn and what kind of work intensity is as a programmer, but no matter how busy the work is, I still have to spare 2 hours a week to study.
Within half a year, you will be able to see the changes!