1. You must not think that learning skills can bring a stable life and a high salary, you do not think that those engaged in market development, running errands, no future.

Don’t know whether you know, we Chinese have a considerable part of the software company, their software development teams are small, even only 1 to 3 people, even not a project team, this team has to bear all the software development of a software company, in the key stage of software packages and development need team members of the day and night to work overtime, Sometimes, if you’re unlucky enough to join a field development team, you’ll have to leave your hometown and say goodbye to your girlfriend, do closed development, and all you do is code and eat and sleep.

What’s more, the relationships you will be exposed to will be very simple, you will hardly meet people in other industries and positions except limited technical staff, your circle of friends will be small and simple, and even destroy your original love.

Maybe you get the so-called white-collar salary, but you lose the freedom to enjoy life. If you want to be a technician, especially a developer, I think you will soon understand how much you want to stay in one place for a long time, meet some friends, and live more.

Than our lives and relationships, and job, those of you who is engaged in the pre-sale and market development, there are more than we more time outside of work, and even their working time is sometimes and life time can be both, they can through the market development, meet people in a wide range of industries, can meet all kinds of friends, They have a better chance of getting rich and developing than we do frankly, provided they work as hard as we do. (There is a kind of industrious common man, if you change his place, he will soon become a diligent and outstanding man.)

Never learn skills thinking that if you are the most skilled, you can become 100% respected.

Once a man said in an interview for a project manager, “I only use the most obedient people and follow my requirements as long as they are obedient, and if not, no matter how good their skills are, I don’t want them. Then this guy gets a tryout and, if nothing else, he’ll be the next project manager.

You know what, guys? No matter how skilled you are, you’re not free to take the time to dig into LINUX source code like everyone else, or even write a Linux-like masterpiece to show off your talents. Need to do is to write code in accordance with the requirements, the meaning of writing code is a specification, in accordance with the specifications you write, you will soon find you write the code yesterday, and today there are many similar code, the code you wrote for a period of time, you will enjoy: copy, copy, paste that technology is important to you.

If you’re lucky enough to hear marketing people talk, or leaders talk, you get the sense that they’re treating technicians like coding machines, and that your value isn’t as important as you think. On your team, you may be fighting with your colleague over a technical issue because he disagrees with you and you disagree with him. You both think you are right, but you are both right, and the purpose of the argument is to prove that you are better than the other person in a critical situation.

You do not think, if I am good enough technology, I will start my own business, their own entrepreneurial capital, because they are engaged in technology.

If you think that, you are wrong, you can do a survey. Few people in the non-technical community know C# and JAVA, let alone appreciate whether your technology is good or bad. In a word, technology is just a tool. People who are good at using this tool to work for others are often not good at using this tool to start their own business, because these are two concepts and the skills trained are completely different.

Start a business in the beginning, your relationships, your ability to handle interpersonal relationships, and your understanding of the social rules, and you understand not understand other people’s heart, you can speak to people like it, and you for services provided by the planning and promotion, etc., may ten thousand, one million worth our attention problems, But what you find is that technology is rarely one of those ten thousand or a million, and if you get to a stage where you’re starting a startup and you say to yourself, “Why should I do the technology myself, why should I hire someone?” that’s when you really understand what technology does, and what you used to do as a tech person.

The last

Technology is just a tool, a tool to survive in a stage of your life. You can like it all your life, but it’s better not to live on it all your life.

The only purpose of mastering technology is to get a job (if you don’t want it to be your second life), to get work. So when you are studying, do not go to do those so-called technical problems or study those bubbling algorithms, maximum number algorithms, what is work?

Is to make something for others to use, others use, can improve their work efficiency, think about it, you do ten thousand technical exercises what use? It will only make people feel sour, or in the learning time, more cultivate some of their pragmatic attitude, such as research the local market which software companies employ people, how far they are from their requirements, their specific should do to meet their requirements. Once you’ve analyzed all this, you’ll find that technology doesn’t contribute as much to job success as you might think.

Whether you’re learning technology to get a job or start your own business, you need to be aware of the technology itself.

conclusion

“Never live by technology all your life” is a realistic statement. Many people think they are in their 20s and earn $2~ $3 million or more a month, which is OK.

This sentence is best understood if you are not satisfied with your current salary (if you have worked for a shorter period of time, you can check to see if you are satisfied with the salary of people who do well in the industry) and are worried about your future or your industry.

That’s why most people who understand it are in their mid-thirties. Admittedly, for a programmer who has been working for 7 or 8 years or less, this stage technique is a must. To have the technical ability to be fired today, I can guarantee to find a job tomorrow; If you’re lucky enough to have someone who’s an expert in a field that can’t be replaced by someone younger than you, the phrase “don’t rely on technology for a lifetime” certainly doesn’t apply to you. However, for most of us, being irreplaceable in one area (opportunity and talent) is not an option, so we need to find ways to ensure that we don’t get laid off, that we don’t lose money, that we don’t lose quality of life as we get older.

If at this stage you are still trying to figure out how to implement this feature and how sophisticated this algorithm is, I think you are either too simple or you are using technology to escape reality. To put it mildly, all I think about is how to make money and how to make my family’s life better. The tech guy didn’t reach this point before 35 (regardless of financial freedom). Do you think there’s a chance after 35? Or ask yourself how much of what you are doing is what you can do, what others can’t do, and how much technical content you should have in mind. So, technology is just a skill for making a living at this stage.

Everyone’s skills have a ceiling. When your skills reach the ceiling, you need to consider whether your income can meet your needs. Of course, if you have a mine at home or a couple of apartments on Beijing’s Second Ring Road, you can make technology your hobby.

Private letter reply data to get a line of big factory Java interview summary + Alibaba Taishan manual + the knowledge points learning thinking guide + a 300 page PDF document Java core knowledge points summary!

These are some of the things that the interviewer should ask during the interview. These include basics, Java collections, JVMS, multi-threaded concurrency, Spring principles, microservices, Netty and RPC, Kafka, diaries, design patterns, Java algorithms, databases, Zookeeper, distributed caching, data structures, and more.