This is the 10th day of my participation in the More text Challenge. For more details, see more text Challenge

Personal profile

One for students with poor grades and a graduation from an airport school in June 2017. I have been engaged in Android development for 4 years, developed set-top box applications, and made mobile phone apps. After 21 years, I joined a new company to develop vehicle-mounted applications.

Work experience

Because the new company entry is not the main talk about the previous work.

Suffering & Not much growth (first company)

I am in this state not because the company is bad, but because OF my own poor performance. When I was in the company, the company has a perfect training mechanism (you can also choose some training in other directions, which will be taught by senior developers from other departments), and the corresponding mentors will provide training when you enter the company. What’s even happier is that every month the boss will buy books for us to read.

Since in such a good environment why AM I still so uncomfortable? There are the following reasons for the conclusion.

  1. Your mind is cluttered. Python, JS, the Web all want to learn, and the end result is nothing.
  2. After work, I spend a lot of spare time playing games.
  3. My technical foundation is not enough, but I choose the wrong things to learn, resulting in the main work did not make good results. The end result is being dragged along by the company.

Thrive & develop

The reason why we should add the word “strong” before growing up is because the personal technology is growing much better than the first company.

In 2018, I was lucky enough to get in touch with time management and began to learn to adjust my own state. Study in a planned and purposeful way. I would arrive at the company one hour in advance every day to read technical books. Two years to finish the technical books

Exploring the art of Android development

Talk about design patterns

Android source code design pattern

Android advanced decryption

As time went on, I became the main developer of the project from a supporting role in the project team. At the same time, I grew to the intermediate level of development, and I also had some technical communication with junior partners.

Compared to the first company, there was no technical training or mentoring. But my technical growth has been relatively large. Personal understanding is: internal drive is greater than external.

outlook

Interviews began in March. There are about six interviews before and after the interview, through several companies interview also have a general understanding of their value (how much money). One of the most regrettable is the interview notes, the first three rounds of technical surface has passed, the result of VP failed. It could be that you’re being too motivated because you really want to go, and you’re even prepared to take a pay cut if you can.

Compared to the others in the company, my interview process was relatively smooth. I think the best thing is that we should not prepare for the interview, but focus on accumulating our skills.

Things to do in the future

  • Learned data structure 678 months brush leetcode hottest 100 questions
  • Source code reading summary
    • Operating principle of Bluetooth application layer (completed in June)
    • System Binder mechanism
    • System Anr principle
    • Some other framework source reading

Tips for work

  1. If you are just starting out, it is advisable not to spend too much time researching other things when your expertise is not so solid, but to focus on improving your expertise
  2. With regard to the learning of workplace skills, we should remember that our learning is all for a purpose, and we must sum up after learning. Don’t start over again.
  3. As for the choice of work, my understanding is that it is suitable and best. It’s like putting a very bad student in a very good class, and he can’t keep up with the teacher. It takes a lot of time to catch up, and adults often lack that time.
  4. In terms of data structures and design patterns, many people who have been working on them for years say they don’t matter. For a simple example, how do gradle projects determine circular dependencies? Learned the knowledge of graphs, understand topology sort. You’ll see that this is at least one way of judging circular dependency. Without understanding them, a lot of times they just stay with API calls. Knowing the data structure allows you to write something deeper.
  5. Finally, calm down and do what you want to do. Every goal needs little by little effort.

Thank you for reading here, if you think the article is good, or you have a little inspiration. Welcome to like and retweet.

That’s four years for an average Android developer.

I hope to have the opportunity to disembark in Dafang.

The problem

Finally, can you get $2W per month in Chengdu with 5 years of Android experience?