Discussion

When to quit?

I have a slight dilemma... I was brought on as a software engineer for a large company back in September. I was an intern for this company for ~2 years prior and had a great time working there, until I started full time.

The team has changed drastically since I started interning there. In the beginning, we did all of our development in-house with ~5 engineers + myself. I was able to get help anytime I needed it, but now 99.9% of the development is done off-shore.

I'm now the ONLY in-house developer with NO understanding of the current applications we're working on. Not only that, but we've switched technologies from Rails to Spring. I'm really good at Rails/Ruby and can work on those types of applications without much help at all. When it comes to the new stuff, I take in a deep breath and then think to myself run away as fast as possible.

The new code has almost no comments. The new code almost ALL needs to be refactored -- and this is landing on my shoulders.

My question to the community is this... when should I quit? I want to leave ASAP but I have no other job offer on the table. Every day I come to work and ask myself "why the hell am I here?" because they don't need me. If I dropped off the project, nothing would really change because I haven't contributed anything to the project and I'm having a lot of difficulties learning from the devs -- especially when I can't even learn from the code base.

I started this job ~3 months ago, so would it be legit to just remove it from my resume and spend my time finding a new job?

Help!

18 points djmill 12 years ago 34 comments

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton