Those who write job-hopping answer, which have so simple, job-hopping is not omnipotant.
Job-hopping is to raise salary fast, but, normally, job-hopping salary can only rise 20-30%, calculate by 30%, need to jump 3 times to double, jump a year, need 3 years; It takes six years to jump every two years.
Some people say you can go up more if you jump to the big factory. Ok, if you jump to the big factory and you go up 50%, you have to jump twice. At the same time, the big factory will mind your frequent job-hopping, and there will be no interview opportunity at all if you frequent job-hopping, such as JD’s explicit requirement to reject candidates who have been job-hopping for less than two years.
So be careful when it comes to job hopping.
A surer bet than job hopping is to move up within the company and get a bigger raise as you move up the ranks.
So how do programmers get promoted quickly?
The answer is: make yourself a good programmer
What’s the difference between an average programmer and a good programmer? Consider the following comparison between two programmers:
W: An ordinary programmer
Xiao L: Excellent programmer
1. Differences in code quality
On the Bug management platform, Little W’s bugs are one by one. Many bugs are caused by errors in the results returned by method calculations in the code. The input values that cause these errors are neither extreme values nor weird boundary conditions, but normal business parameters.
What does that tell us? It shows that Little W was lazy not to write unit tests, and even didn’t take the tests himself, waiting for others to test them for him.
Small L’s code is very robust, and in the Bug platform, small L’s code has very few bugs. If you look at Git of your project, you will find that the unit test code of small L is very large, even far beyond the project code.
2. The difference in development speed
From the project management platform, you can see everyone’s development time statistics. A similar requirement, little L takes half as long as little W.
For example, the last project needed to connect two new third-party channels. Little W and LITTLE L each made an interface with similar parameters and process. It took Little L 3 days and little W 5 or 6 days.
In addition, when the interface changes in the later period, each time small W needs to change for two or three days, while small L only needs half a day.
The reason is that every time little W writes code, it is particularly inelegant and inflexible. A little change requires a big change, and it often changes bugs.
However, little L always starts to write after thoroughly thinking about the scheme, and keeps refactoring the code. The final code is flexible and elegant, and it can be changed as soon as the requirements change.
3. The difference between rigorous thinking
Once, little W wrote an external interface of the public platform, finished and took it out for testing, the result made a big joke. He wrote the external interface without even a signature to verify it. Fortunately, it was found out during internal testing. Otherwise, the professionalism of the entire team will be called into question.
While little L also writes an interface, not only considering the problem of verifying the signature, but also considering that the parameter needs to add a timestamp to ensure that the signature will not be reused.
4. Differences in teamwork
Open Git for their project, look at the public utility class, little W has not committed a single line. Then, open a part of the code at will, so many can share the code, little W has never thought to come up with a tool to facilitate others. Just stick to your own business, finish the work. Code style, reuse, and teamwork were all thrown out the window.
Small L is not the same, not only will take the initiative to write some tool classes, sometimes will make some small framework, reduce the development of others.
5. Differences in business understanding
In the demand meeting, Little W never seriously participated in it, and rarely communicated with the product manager to analyze the demand actively. When you start writing code, little W is either implemented differently or missed.
There is a need for permission management, which was originally W’s responsibility.
The result is that this function, the permission configuration even does not have a background, the service has no place to configure the permission. In this way, little W also said that the function is finished, but also quarreled with the products. The final result is to be slapped in the face, someone else’s product prototype diagram and requirements document said very clear, but also held several requirements analysis meeting, we all understand, little W appeared a problem.
Small L, on the other hand, attaches great importance to business requirements, writing out some documents and outlining the design implementation to pull the product check. If there is a problem, we will call the product and operation to have a meeting at the same time, and make sure that we form a consensus, and then start to implement.
Small W failed the rights management development, small L took over. He drew a diagram of roles and permissions, and then went through it all with the product. After confirmation, email consensus, and then develop. Everything is going well.
6. Differences in work Attitudes
Want to know, although product often offend technology to hate, but, everybody is ordinary person, natural also have unexpected place. Generally speaking, Xiao L will cooperate with the product. When the product is unexpected, Xiao L will actively communicate with the product to find out the gaps and fill the gaps. However, when it comes to little W, things often cannot be pushed down.
There was a feature where the product requirement was to be able to notify other parts of the company when there was a change in merchant information. To inform other systems, it needs to connect to the company’s unified public messaging system.
In this case, Little W directly said to the product “docking is very troublesome, the other side does not cooperate”. Although it is sometimes difficult to work with other departments, this is not a reason to put things off. It wasn’t done until people asked about the progress.
After I gave the job to Xiao L, she explained the reasons and problems to the product in the first time, and then held a meeting to coordinate a new launch time and schedule the workload of connecting to the public information system.
Later, Xiao L temporarily moved the station to the team in charge of public information system and developed it on the spot. The matter was settled properly.
7. Differences in problem solving skills
Belong to the same technical team, small W encountered problems, go to the crux of the problem, a technical problem, can cut for a week, as a result, other work is also delayed.
Once, little W encountered a problem with the output data being out of order, and then, when he debugged, he couldn’t find the problem anywhere. On this, ink for a week, later is small L take the initiative to ask him why, just know the problem he encountered. Several people in the team helped him troubleshoot the problem and solved it in two hours. And he’s already a week behind on his work.
When encountering technical problems, xiao L would first try to solve them by himself. If he found that he could not solve the problem and there was a risk of progress delay, he would immediately seek help from the team master and the technical leader. In short, he would try to solve the problem as soon as possible so that he could move to the next step of work.
Here’s one last way to double your income or get rich:
The opportunity to pick up some company stock or options
A year or two ago, ByteDance programmer Guo Yu, 28, was financially free when he announced his retirement.
Two quick points about stocks and options:
First, now the Internet industry to the stock, the option of the company is not uncommon, reserve some knowledge in advance, in case the future talk about offer when these words, you will not understand what also.
Second, I feel that I am still very vegetables, the company’s stock, options are for the core employees, not their own. Now the food and how, who is not from the food to become strong, now no stock, options, does not represent the future will not get.
Recommendation: # talk about “freedom” it | technology today don’t chat, talk about the end of anxiety
At the end
Public number: xiao He growth, The Buddha department more text, are their own once stepped on the pit or is learned
Interested partners welcome to pay attention to me, I am: He young life. Everybody progress duck together