Also iOS programmer, where is the gap between 6K and 30K? Why is the pay difference so big?

Objective:

Some people see this problem, the first feeling of the answer is "because you are a junior engineer, he is the engineer Bai ~". This is really a good answer! No matter what kind of occupation has a process from "beginner" to "advanced", no one can skyrocketing rise, born to be an architect or CTO. So how do you go from beginner to advanced? How can we accomplish this transition phase in less time? Today is the same program ape, the gap between 6K and 30K in the end!

As a developer, there is a learning atmosphere with a communication circle is particularly important, this is a My iOS communication group: 638302184, whether you are small white or Daniel Welcome to settle, share bat, a inside test, interview experience, discuss technology, we exchange learning and growth! Hope to help developers less detours.

1, work experience and technical accumulation

When it comes to senior engineers, the first impression is that the work experience is rich and the technology is awesome.

Note that this is about working experience, not about working hours. Some people down to do projects, spare time to learn more new technology, insist on reading, earnest blog summary, more practice, plus their own perception is not bad, 2, 3 years of time can have others 3, 5 years of work experience, growth for the company's senior engineer. And some people goof around, do the project muddle, spare time to play games, Chase drama, maybe you work in the company for 10 years look conscientious, but you do not have higher requirements for themselves, the status quo, not to seek progress, such people even have 10 years of working time, but can only stop here.

Relying on their own continuous learning, as well as the accumulation of work experience, step by step, see more market, stepping on the pit is more, the technology is more and more well-deserved thing, and technology is a senior engineer the most basic requirements, but I think as long as not fool, to the technology a little pursuit of people, want to achieve this is not difficult, Just the length of the problem, in addition to technology, you and those real senior engineers there are other aspects of the gap!

2, responsibility

Senior engineer responsibility must be very strong, responsibility is to reflect a person's attitude problem, for a bug, they will always pay attention to, want to do everything possible to find the cause and solve, and some people for the bug is muddle through, the attitude of solving the bug is to try, think from the surface to solve the OK.

Our CTO more than 10 years of software development experience, there is user feedback bug, no matter how busy, no matter what time, must stop the things on hand, to find the cause and solve. My experience in mint, has been more than once with him in order to solve a bug late at night, there are a few late night to find a cause users can not pay the bug, I lay in bed, the CTO shouted up to the company to repair the experience, at that time, I did not understand the long, I realized that this sense of responsibility is professional accomplishment , is now also deeply infected, at any time, anytime, my mobile phone, computer is not away from the body, the problem must be the first time to respond!

In contrast to you, are you responsible enough?

3, Active

Is there such a experience? Is the project finished, feel nothing to do, then brush micro bo, chat QQ bar.

But what about the good engineers?

When they finish the project, they think about where the code is not good enough to focus on.

I was in a hurry to catch a function, just use this time to see if there is a better way to achieve.

This project finished, learned a lot of things, and stepped on a lot of pits, write blog summary. Multi-bubble Technology forum, such as Dbaplus community, csdn this, less brush dot Weibo!

Finish this project feel the knowledge of the architecture is very short, I quickly learn the relevant knowledge it.

Usually have time to go to see the excellent engineer's article, if can participate in their speech that is again good! Learn more about the industry big coffee to pass out the information, in this fast changing ERA is particularly important!

The junior engineer is waiting to be assigned the thing to do, the assignment of the thing finished feeling there is nothing to do. And the senior engineer will take the initiative to do their own job, they will never feel their time superfluous, refactoring, optimization, learning, summary and so on, there are a lot of things you can do on the initiative.

4, Dare to bear

Junior Engineer in a slightly more complex point of demand when the first impression is so complex, I can not achieve, even if this technology to prove that the other could be achieved. And the senior engineer will not do not do technical research to say no, dare to accept the challenge, unless you have done a full technical investigation, convinced that it does not happen, otherwise will pay 200% of the effort to achieve it.

For the technology so, the same for some solutions, architecture design, the problem of historical issues and even the project leader and other challenges will be the courage to bear, you do not force yourself, give yourself a bit of pressure, you never know how much your potential, and is in this process of overcoming difficulties, your growth is rapid!

So, try to take on some challenging work for yourself!

5, Team work spirit

Now this era is no longer a heroic age, the team is everything, you can be superior, but compared with a team, you are outnumbered. Therefore, the excellent senior engineer always have team spirit, always take the team's interests as a priority, any time, do not drag the team hind leg of that bit!

The cohesive team is a company's most competitive core weapon, so please let yourself have this consciousness from the thought, the team is always bigger than the individual!

6, participate in business, product

I've seen too many programmers, product manager to give the demand, the bulkhead began to write code, midway demand changes, and then began to scold product manager in the heart Silly X, is simply the so-called "yards nong", although we all take "yards nong" to self-deprecating, but I believe we do not want to become the real code farmers, we have to do is engineers!

And the difference between engineers and yards, they are not only Coding, they will participate in products, participation in business, although our main responsibility is to develop, but if you can discuss with the product manager in the demand phase, perhaps in the product, business you are not professional, but you can think from a technical point of view, participate in, Try to help make the demand more perfect.

The junior engineer gets the demand directly, and then does the discovery of a problem, either the technology cannot be implemented or the logic is problematic.

And the senior engineer to get the demand will consider a lot of technical feasibility? Do you have any help with your existing business? What is the impact on the existing technology architecture? What about extensibility? Wait a minute... Then the design coding phase will be followed.

So good engineers can have a great help to the product, but also with the product manager to communicate more, in addition to technology, on the product, on the business, on the business you can learn a lot of things, the future road will be wider.

Therefore, do not do the Coding of the yard, do care about the business, product engineers!

7, summary

The above is my summary of the excellent senior engineer some of the standards, do not always say you and those people is only a technical gap, in addition to technology, other places may be far worse.  Technology can rely on time to make up, but the other aspects of the time can not be compensated, I hope that we control, whether it is the so-called senior engineer, or after the group Leader, or even after the architect, CTO, these qualities are must have, ask yourself, how far is your gap? If you have a better idea welcome to add ~

As a developer, there is a learning atmosphere with a communication circle is particularly important, this is a My iOS communication group: 638302184, whether you are small white or Daniel Welcome to settle, share bat, a inside test, interview experience, discuss technology, we exchange learning and growth! Hope to help developers less detours.

The article originates from the network, if has the infringement, please contact the small compilation to delete.

Also iOS programmer, where is the gap between 6K and 30K? Why is the pay difference so big?