When to Quit Your Job and What a 2‑Year Java Developer Should Know

Hello, I'm 歪歪. A reader with two and a half years of experience asked about "裸辞" (quitting without a new job). I initially advised against it, but the reader insisted on resigning immediately.

I stress that quitting should only be considered when the current job severely harms physical or mental health; otherwise, it often leads to financial, psychological, and social pressure.

Do not quit unless absolutely necessary.

Have a solid financial cushion before resigning.

If you must quit, do it early in your career when the cost is lower.

For most programmers staying in the same city and role, I strongly recommend not quitting because the psychological stress of job hunting can be overwhelming.

Economic pressure is the easiest to manage; the biggest challenge is maintaining a healthy mindset during the job‑search gap.

When the job search drags on, anxiety, self‑doubt, and negative emotions can impair performance in interviews.

Therefore, keep a strong mental attitude, and if you have sufficient savings, you can afford a longer search.

For developers with two years of experience, the key technical foundations include:

Solid computer fundamentals: data structures, algorithms, operating systems, networking, databases, and Java basics.

Proficiency with common development tools such as Maven and Git.

Java proficiency: OOP, multithreading, reflection; familiarity with JVM tuning, class loading, NIO/AIO, bytecode enhancement is a plus. Familiarity with the Spring ecosystem, Servlets, HttpComponents, Guava, etc. MySQL development, understanding of transaction isolation, indexing, performance tuning; knowledge of NoSQL is beneficial.

Understanding (but not necessarily deep experience with) middleware like message queues, sharding, scheduling, distributed configuration, and basic SOA concepts (RPC, serialization, service governance).

Interview preparation should cover both core knowledge and broader topics to demonstrate technical breadth.

Beyond technical skills, emphasize project experience, business understanding, and soft‑skill development.

Finally, a piece of advice for 1‑3‑year developers: avoid getting trapped in pure technical work, broaden your perspective, engage with more experienced peers, improve soft skills, and take care of your health.