android environment configuration! Master these hot cutting-edge knowledge of Android development, this reason I am convinced

beginning

This is the era of making fine products, not the era when a product could attract investment and cheat clicks. Boutiques need more professional talents, that is, the requirements for the quality of APP developers will be higher, and the market will return to a normal rhythm. How much money is taken depends on the ability and the product. I think this is a good thing. The big waves are scouring the sand. The rest should be people who love the industry and have good talents. It must be a good thing for the industry. For the individual, the environment is better.

1. Pursue high salaries

Compared with small factories, the salary level of large factories will be much higher. The specific number range will not be elaborated, but the big factory will be more generous as a whole. As long as you can pass the interview, you will have a chance to get a salary increase of 30% or higher. What's more, the year-end bonus of the big factory will not be awarded "Unscrupulous" the boss arbitrarily deducted.

2. Pursue stability

Last year, the overall environment was not good. Many companies laid off employees, especially small and medium-sized factories that were not profitable, such as a certain group and a certain drop. For large companies, the probability of layoffs will be much smaller. After all, the benefits of layoffs are far less than the negative effects and stock price declines.

3. Pursue career development

In the past two years, many fast-growing companies have used double salary to dig people at BAT, such as Toutiao and Pinduoduo. Therefore, from the perspective of long-term career development, BAT's work background is as popular as a graduate of Qingbei. With the background of BAT, no matter whether you are hopping or promoting, becoming a technical manager or architect in the future, you will have enough initiative.

There are also many people who say that the big factory is talking about making rockets in interviews and screwing in the screws. It
happened that a friend of mine happened to be engaged in research and development in Ali, and I would like to talk about the following opinions with you today.

4. Are there screws in big factories?

When some people mention a big factory, they will immediately say that they can only be used as a screw and repeat the same work every day. In fact, this idea is very one-sided.

The traditional big factories are generally hierarchical, and the things to be done are highly repetitive and mechanized. That's because those fields are already formed and lack the motivation to innovate, so many people are forced to become screws, and only need to ensure that the machine can run.

But this is not the case with major Internet companies. We are among them and we should know that Internet technology is changing with each passing day. Everyone is shouting "I can't finish learning", and Dad Ma also says every day that we need to innovate to adapt to the times. In such a rapidly changing industry, I am afraid that it is not easy for you to just be a screw.

Within Ali, everyone is used to embracing change. Change means business changes, technology changes, and personnel turnover. In such a fast-changing environment, if you just want to be a screw and repeat the same mechanical work every day, it is either that you lack initiative or you are willing to be a screw. Of course, screws often fail to achieve good performance.

5. Are the employees of big factories very narrow in technical contact?

Of course, some people have said, "What I call a screw is not to do repetitive mechanical work, but to say that only a small piece of business or technical point can be contacted, and the whole picture of the system cannot be contacted."

This is indeed a fact, after all, big factories have a lot of R&D personnel. Therefore, a complex system is usually disassembled into multiple parts, and each group or each person will make one of them.

But what I want to say is, can you not grow if you only touch one area? What is the biggest difference between a large factory and a small factory? Is the user level. Generally, small factories have hundreds of thousands or hundreds of thousands of DAUs, while large factories often have tens of millions or even hundreds of millions of DAUs. The same piece of code can run well in small factories, but when you reach large factories, you will find that it is inside. There are many problems.

The big factory seeks proficiency and depth; the small factory seeks speed and breadth.

If you are in a large factory, you should study the modules you participate in as deeply as possible, and think about how to optimize the modules you have made to the extreme so that they can still run stably in the face of a huge number of users. Believe me, such an experience can be a highlight of countless interviews in the future.

6. Small factories can be exposed to all kinds of trendy technologies, but big ones can't?

Indeed, in terms of attitudes towards new technologies, small factories tend to develop more than large factories. After all, the boat is small and good to turn around.

I believe that many readers also have "interesting" experiences similar to the following:

It was a good idea to study what the paradigm is in Java. Suddenly my colleague ran over and said: "Java is out, everyone is using Kotlin! It's so cool to fly".

So, you researched and found that Kotlin has so much syntactic sugar, and it seems to be much smarter than Java.

Therefore, you can encourage the whole team to learn Kotlin together, share various novel uses of Kotlin, the team is happy, and enjoy the joy of technological growth together.

Two days later, the team leader ran over and said: "You are still writing Android, everyone is using React Native, and both ends of a code run at the same time!".

So, you study it again, RN is indeed a good thing! Write a copy of JS code to run on both Android and iOS platforms at the same time, which is very convenient. And many well-known companies such as Airbnb are using it.

Therefore, you urge the whole team to abandon Kotlin, learn RN together, and share novel usages such as RN hot update, so the team is happy again and enjoys the joy of technological growth together.

After another two days, the Internet tycoon shouted: "RN performance is too bad, we have to return to Native, Native is the king."

At this time, you didn't think too much, because you also think that RN's performance is really bad, and you heard that Airbnb has also given up RN.

So, you go back to write Java.

Later, someone said to you, go learn Flutter, it will be too late if you don't learn it again, and Android will get cold sooner or later.

You: Haha.

In the above paragraph, you may have been exposed to similar scenes more or less. Of course, the main point I want to explain here is that small factories do have a broader technical scope and diverse technical options, because even if you choose the wrong one, you can always turn around and change it again.
But what I want to say is, even if you have been exposed to so many kinds of technologies, and finally calm down and think about it, how much have you learned? Apart from the fancy "new trend nouns", what have you really gained? Does such a technical aspect really help a technical career? I don't think so.
In large factories, some people spend more than half a year studying how to withstand higher concurrency under the same machine resources; studying how to maintain the fastest network connection speed under a complex mobile network;

summary

Of course, what I want to say is by no means not to learn new technologies. As a technician, it is very good to maintain sensitivity and awe to new technologies, but never blindly worship or follow the trend of new technologies. You think that new technologies must be good. This will only make you fall into a whirlpool, shouting again and again that you can’t learn, and again, your body will run with the wind without knowing the Lord

Recommended learning materials


  • Brain Mapping
    360° all-round performance tuning


    Due to the length of the article click on the link to see the problem and obtain detailed study notes articles: GitHub

%A6%82%E4%BD%95%E9%9D%A2%E8%AF%95%E6%8B%BF%E9%AB%98%E8%96%AA%EF%BC%81.md)**

Guess you like

Origin blog.csdn.net/a120464/article/details/114098287