There are often programmers discussing whether to resign and whether it is a wise move to resign now. This is a very serious topic, because this decision will have a profound impact on the programmer's career and life.
Many people want to quit their jobs but stay away because they are afraid of being labelled as "love to change jobs." From the results of my observations, many programmers tend to stay in the old company for the so-called "reputation", but compare the two in the later period, the programmers who "stay in the old company" have experience in handling problems and career development The prospects are far inferior to those who frequently change jobs. As I said before, some companies are even very willing to see some positive staff turnover in their positions.
Programmers usually resign for some of the more common reasons (such as failed product releases, layoffs, reduced salary/benefits). One might say that the value of the experience learned in a company on the verge of bankruptcy is far greater than the experience in a successful company. However, if you wait for the "resignation" alarm to sound and you happen to encounter a false alarm, your career will be overwhelming.
When should I consider resigning?
First of all, you have to have become the "best" programmer in the company, or you can no longer find someone who can be a teacher and mentor
On this point, many people are overconfident, so we need to honestly evaluate our skills. Furthermore, even if you admit that you are not the best, are the "predecessors" you consult willing to share their knowledge with you? Yes, even if the company you work in employs talented people with unique skills, but if these people are busy with their own tasks, and you are not at a loss, then what is the difference between this and working alone?
If the technology used is not sustainable, you will eventually be eliminated by the market
If you are still stubbornly obsessed with expanding these outdated, proprietary or very special technologies, then you are digging your own grave. If any company is still using an early version of a certain language or framework, that might just be able to save you. However, you have to understand that staying in a stagnant technology environment for a long time is much worse than working for the same company and constantly improving the tools for them.
If you do nothing
This may not be your fault. Because it is possible that your company has been delaying the release, or has always been unable to deliver in time. These problems originate from the development process and management decisions, and have nothing to do with technical personnel. If you look back at the minutes and seconds you spent in a company, and suddenly find that you haven't made the slightest meaningful achievement (the time should be long enough), then I advise you to think about the issue of "resignation".
If your problem is low salary and no room for promotion
Then at least there must be a reason for being lower than the market price. For example, being able to work with some exceptionally good people may be the number one reason, and learning valuable skills and experience comes next. If you don't make much money and don't have any positive future plans, then it is time for you to reconsider your choices.
If some good projects and promotion opportunities are always out of your turn, your ideas are always out of consideration
This shows that you are not important in the eyes of the company. They think you are good enough for your job, but they never see you as long-term capital that is truly worth investing in. If so, you can send your resume to the new company.
If you are in the same situation as you just joined the company
The so-called "condition" here has many meanings. The traditional above refers to the financial situation (you have to give you a salary increase), and here we give it a deeper meaning, that is, technical ability, market competitiveness, etc. If these aspects still haven't improved after a period of time, then I want to ask you, where else do you have to stay?
If there is no change in your work day after day-if you only need to be responsible for some trivial matters for a long time, it will gradually obliterate people's will and become degenerate. The culprit is that you are always responsible for a small part of big projects and important products.
If you have no passion
Many areas of software development are not as interesting as outsiders think. In this case, if you have the opportunity to challenge the technology around you to make some real innovations, it may help to adjust this state of sluggish fighting spirit. But if you feel that your current work is worthless and can't spark inspiration at all, then you might as well jump out of that circle and find something that interests you.
English original: When To Leave Your Programming Job
personal homepage: http://www.howardliu.cn
personal blog post: when should programmers consider resigning
CSDN homepage: http://blog.csdn.net/liuxinghao
CSDN blog post: programmers When should I consider resigning