Many people want to quit their jobs but are held back for fear of being labeled a job-hopper. From what I have observed, many programmers tend to stay with the old company for the so-called “reputation,” but later in life, the “old company” programmers have far less experience solving problems and career prospects than those who change jobs frequently. As I’ve said before, some companies are even more than happy to see some positive turnover in their positions.
Programmers often quit for common reasons such as failed product launches, layoffs, salary/benefits reductions. One could argue that the lessons learned at a failing company are far more valuable than those learned at a successful one. But if you wait for the “quit” alarm to go off and you happen to get a false one, your career will be ruined.
When should you consider quitting?
1. Either you’ve become the “best” programmer in the company, or you’ve run out of teachers and mentors
Many of us are overconfident about this, so we need to honestly assess our skills. And, even if you admit that you’re not the best, are the “older people” you approached willing to share their knowledge with you? Yes, even if you work for a company that’s filled with talented people, if they’re going their separate ways and not giving you a second thought, what’s the difference between working alone?
2. If the technology you use is not sustainable, you will be obsolete
If you persist in extending outdated, proprietary, or very specific technologies, you are digging your own grave. If any company is still using an early version of a language or framework, that might just save you. However, you have to understand that being stuck in a stagnant technology environment for a long time is far worse than working for the same company giving them tools to improve.
If you don’t succeed
It may not be your fault. It could be that your company is dragging its feet or never delivering on time. These problems stem from development processes and management decisions, not technical talent. If you look back at every minute of your time at an organization and realize that you haven’t accomplished anything meaningful (long enough), you might want to think about quitting.
4. If your problem is that you are underpaid and have no room for advancement
Well, at least there has to be a reason for it to be below market price. For example, being able to work with some particularly great people might be the number one reason, followed by learning valuable skills and experience. If you don’t make much money and don’t have any positive plans for your future, it might be time to reconsider your options.
If you don’t always get the big projects and promotions, your ideas aren’t on the table. It means you’re not important to the company. They think you’re good enough to do your job, but they don’t really see you as long-term capital worth investing in. If so, it’s time to send your resume to the new company.
5. If you’re anywhere near where you were when you joined the company
Here the so-called “status” have many meanings. Tradition refers to the financial conditions above (have to give you a raise water), here we have the deeper meaning, namely, technical ability, market competition, etc. If these aspects after a period of time still not improve, then I want to ask you, do you have any reason to stay in where?
If you do the same thing day in and day out — doing the same little things over and over again — it wears down your spirit and degrades you. The number one culprit is that you are always responsible for a small part of a big project or important product.
If you have no passion
Many areas of software development are not as interesting as outsiders think. In this case, the opportunity to challenge the technology around you and make some real innovations may help to correct the demoralize state. But if you feel that your current job is worthless and completely uninspiring, go outside and find something that interests you.
7. You want to take things to the next level
Have 1-5 work experience, don’t know where to start in the face of the current popular technology, need to break the technical bottleneck can be added. After staying with the company for a long time, I was very comfortable, but I hit a wall in the interview when I changed my job. Need to study in a short period of time, job-hopping can be added. If you have no working experience, but the foundation is very solid, Java working mechanism, common design ideas, common Java development framework master proficient, can add. Think oneself very good B, general need can handle. But the knowledge points learned are not systematic, it is difficult to continue to break through in the field of technology can be added. Group number: Java Architecture Group 650385180 Note good information! Ali Java senior cattle live explain knowledge points, share knowledge, years of work experience sorting and summary, with everyone to establish their own technical system and technical knowledge in a comprehensive and scientific way!