A lot of times we will talk about the application, interview topics. In fact, there are a lot of topics to talk about and things to think about. Many people want to quit but are afraid of being labeled as job-hoppers, so when should programmers consider quitting?
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 the technology is not sustainable, you will be obsolete. Proprietary or very specific technology, then you’re 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 are in the same situation as you were when you joined the company. Traditionally, it refers to financial status, but here we give it a deeper meaning, namely technical ability, market competitiveness, etc. If these things don’t improve over time, then I have to ask you, why are you staying there? 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.
No Passion Many areas of software development are not as interesting as outsiders might think. In this case, a chance to challenge the technology around you and make some real innovations might help to correct the malaise. But if you feel that your current job is worthless and completely uninspiring, go outside and find something that interests you.