"For a programmer, if he stops learning one day, his career will begin to die."
The high-paying IT industry is the career dream of many young people. However, once you enter it, you find that it is not as good as you thought. Known as IT blue-collar programmers, they work hard, like a coding "machine"; technology is updated quickly, and their jobs are unstable. With age, where should Android programmers who have been working for 2-5 years go? It depends on your own vision, courage and opportunity!
I know a lot of good Android engineers, they are not at all anxious, because they know clearly their weaknesses and strengths.
In the communication with them, I summarized 3 points of experience and shared with you:
1. In-depth study of Android underlying framework source code knowledge
Some programmers get scared when they see the source code of the underlying framework and don't know where to start. But to become an excellent Android engineer, proficient in the framework source code is the only way to go.
You have to write more code. If you don’t have time to look at the bottom layer, dig deeper into the principles when you encounter problems, go deep into the bottom layer in programming, and become familiar with the principles. **General programmers do not do it, when you do, you are better than them.
2. Accumulate more project experience
**The ultimate goal of the code is to achieve a solution to a certain scenario. **It's just that if you don't have much experience, you don't know what the code should be. As long as your Android/Java basic knowledge base is solid enough, after entering the company, you will do a few projects. After you are familiar with the framework, you will continue to try to build wheels, and the project experience will naturally increase.
3. Need to master systematic learning methods
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 don’t study it in depth. It is difficult to achieve real technical improvement . It is recommended that you first develop a study plan and associate the knowledge points according to the study plan to form a systematic knowledge system.
end
In a blink of an eye, time really flies. We ran our own things and embarked on our own journey, but even if we haven't seen each other for many years, we are still as "close" as before because of this friendship. Do not forget the original intention and always have to go. Come on, programmers, in my opinion 35 years old, 40 years old is never a crisis, as long as you never forget why you embarked on the journey!
Finally, if you need the same information, you can **Private message I click [ Learn ]** I am willing to share with you!
In order to let more friends who are studying or preparing for an interview see this article, I hope you can comment more, like + forward!
Thanks again to all the friends who have provided me with questions, and thank you for being there!