A Java programmer who has worked for about three years will talk to everyone about his career experience
It seems that this is the most suitable industry, but I can say with certainty: you will really feel this sentence when you are looking for a job after a year of web development.
In the first year of work, it is often a year full of freshness, learning everything, and full of enthusiasm; the knowledge of the WEB industry is updated very quickly. Today is a new version of a framework, and tomorrow is another new framework, sometimes according to the project. I need to keep learning new things; all, many times I feel that I have used so many things! But there are not many things that are really studied in depth.
Interview is the first question that needs to be faced after job-hopping; and different companies have different interview focuses; but there is one thing in common: Java foundation is a must.
In the first year of work, you may ask about your understanding of String object creation, what is the commonly used framework, etc.;
In the second year of work, I will ask you what is the Java memory allocation mechanism, how the classes are loaded, etc.;
In the third year, ask what are your commonly used design patterns, what role do you play in your work, how to complete a module independently, etc.;
It can be seen-this is the growth process of a typical programmer:
Use Java—->In-depth understanding of Java to accumulate experience—>Independent design and analysis capabilities—>A unique all-rounder!
Therefore, you must learn:
Deep understanding of Java basics;
Not much explanation, recommended books "Java Programming Thoughts", "Java Threads", "Java NIO", "Deep Java Virtual Machine"
database
The most commonly used is Oracle (of course, bank projects, etc. require DB2, etc.), proficient in using stored procedures, triggers, etc.;
UML
Documents are often written in projects, the basic skills of project managers, and the basic skills of programmers towards design;
Design Patterns
Look at this suggestion, and experience it by reading the source code;
linux system
Need to master the commonly used linux commands-there are few projects deployed on the windows operating system.
I won’t say much about others, you can add.
In learning, interest is the greatest teacher; project-driven is also a good choice. In short, it is impossible not to learn.
Second. Accumulate industry background;
Industry background is very important; after working for 3 years, you must determine your own industry background, such as having been in the telecommunications industry, in banking projects, in the ERP industry, etc.
Reference: "2020 latest Java basics and detailed video tutorials and learning routes! 》
A programmer cannot write code all the time, that is, when you write code, you must know the business logic and meet what needs; as the saying goes, every line is like a mountain, and the business of each industry is different, even very different, for example, you have been engaged in streaming media. The research allows you to jump to a bank project. When it’s over, learn everything from scratch. The previous industry experience is not needed. Moreover, a company recruits people, hoping to find those who are easy to learn and do not need to train for a long time. Programmers; friends who frequently change jobs must pay attention to this;
If you have been in an industry for a long time, you can become an expert in this industry; we can often see that a leader of a project team writes mediocre code, but can communicate smoothly with customers and control new requirements. , Bug fixes, etc.; and customers are also very willing to deal with him, because those old projects only he can maintain, he is even familiar with the structure of every table in the system-how long can you imagine staying in this industry? .
Third. Reasonable career planning
What is a career plan-is your short-term or long-term career plan! If you don't talk about major principles, let's keep it simple. Let me ask you a few questions first:
a. You have been working for several years. Would you like to be a simple programmer like a newbie?
b. Are you willing to keep writing code without caring about other things?
c. The pre-requirement, design, post-deployment and maintenance of a project, if the leader finds you, you say we can’t figure it out, okay?
Programmers are not machines for typing codes. There are too many things that you don’t understand in the first year. You can follow the boss’s arrangement, type the code, look at the database, test your own and other people’s code; but in the second year, are you still like this? Impossible, you can enter the industry after one year of experience. It's time to learn how to conduct requirements analysis, how to design a database, how to write various documents, and how to write better code? This is a requirement of advanced programmers!
What is a senior programmer?
A programmer who has the ability to analyze and design, can carry out technical research, and has a deep background in a certain industry!
All, after the establishment of a project, you must actively participate in the preliminary design, think and analyze problems with the old comrades, and learn from experience! OK, you will grow up! 
Don't think that programmers just write code! ! !
Moreover, through the development of a project, you need to be able to roughly calculate the development time of a function; for example, a module has 20 small function points, you have developed 80 hours, and each small function point averages 2 hours-then The workload can be assessed in the early stage. Of course, each person’s efficiency and work quality are different and vary from person to person, but the approximate workload should be statistic and used to count the work cycle of a project;
With the above capabilities, you are at least the backbone of a project team! At this point, you can lead the little brother to do development instead of being an ordinary lead.
Many of the company’s project backbones and project managers are not recruited, they are all cultivated-they have worked for 2 years, have good thinking skills, are good at doing things, and are very good! OK, at this time the project manager and the company's middle managers may have noticed you, and they will assign you more tasks to exercise you slowly. Don't be awkward at this time (I once met such a colleague with very good skills and people Yes, the leader suddenly assigned a lot of tasks to him. At first, he silently endured it, and then he made suggestions! After the leader talked to him, he understood it! After a period of time, he basically adapted to it and could finish it quickly; then he became us The new project leader among those people), study hard with the people who lead you, work harder, and get ahead soon!
If you have worked for many years and you are a veteran, you should also be good at leading people and be able to support your younger brother! Because only when the younger brother grows up, the burden on you will be lighter and the project will proceed smoothly!
Moreover, senior programmers (for example, undergraduate) have reached a bottleneck in salary after four years of work (9K—1.2W in first-tier cities). At this time, you must "transform"—senior programmers are only part of your ability, system analysts, Architects and technical directors are the positions you should tell others, and the salary can be increased again.
Fourth. Good mentality and posture
The programmer must be responsible! This point is very important. When you encounter problems, you can't just play the ball casually, communicate with others seriously, put forward your own opinions, and contact customers to solve the problem. The technical problem is not a problem, it can always be solved, but the demand problem must be clarified! Once the requirements go wrong, a project may be delayed or fail. The programmer's sense of responsibility determines his growth. A responsible person may become the backbone and let the leader trust!
The second is to be able to withstand the pressure. Everyone knows that programmers have to work overtime and the pressure is high. All problems must not be easily given up, and they must be dealt with reasonably according to their ability!
The body is the capital of the revolution, and programmers are especially important. Sitting in front of the computer every day, it is easy to gain weight and become a pear shape. So exercise more!
To a certain extent, don’t quit. Stay for a long time in a job that has development prospects or a happy job. You can’t compare enthusiasm with young people. At this time, you want to be steady and act as a senior IT practitioner in the company. , To help people optimize procedures, analyze needs, and make suggestions for projects to solve problems.
Fifth. Write more technical documents
It is a good thing to write more technical documents—in fact, it is a summary and improvement of your work experience! A person who is willing to share knowledge with others can improve in continuous thinking! Moreover, writing documents is a great exercise!
Therefore, I suggest that you do not have a blog or a colleague who often reads other people's documents but does not write by himself. Start a blog as soon as possible. It will be fun!
(Technical documents pay attention to conciseness and conciseness, provide source code; summary documents pay attention to personal experience!)
Sixth. About job-hopping
Job hopping is definitely not an unfamiliar vocabulary for IT people, and almost everyone has done it personally. First of all, I want to emphasize that there is no harm in hopping, but frequent hopping is bad. In the first 4 years of work, you must quit and encourage you to quit (it is recommended to experience 2-3 companies); each company has a different focus on technology and different development process control, so the required technical talents are naturally different ; For example, an outsourcing company wants a code madman (I like to recruit people who have done outsourcing, and I feel that many people who have been in an outsourcing company are very efficient in doing things); small business companies want an all-rounder Programmer (can design and analyze, can write code, can deploy); a large company needs a solid technical and potential person (good English, good understanding ability, and solid foundation in Java); so if you stay in a company After a long time, it is likely to be modelized. If you leave this company, it is easy to get a job sometimes; it is very beneficial for programmers to experience two more companies! And I also feel that every time I look for a job, I force myself to learn something
Original link: https://www.sohu.com/a/271270506_505800