Quitting job because of Java and legacy corporate OSGI codebase. Being junior developer I'm just done with no documentation, terrible team support and non existent code review. After 18 months I can't justify staying any longer. Never had luck with Java and I guess some things just stay the same.

Joined only because of Javascript part, just to be thrown into fullstack position. Stayed way longer because of COVID. Good old simple PHP I loved and foolishly left because of money.

Understandable, could be the best choice for sure.

But to some extent wading through the shit is ... why we're here.

Granted there's varying levels and tolerances and acceptable levels of shit ...

I agree with @N00bPancakes - why regret? Neither Java nor PHP seem manageable in your case.

My regret is that I always expect things get better over time. I can learn from experience a lot. But you have to stop at some point unless things get easier or better.
I don't know, needed to vent after this week.

@hipogo3929

*have a cookie*

Things most of the time don't go the way we want.

It might be time for you to do that thing called prioritizing...

Make up your mind.

What do you expect / want / need?

Does your job fulfill these things?

If not - better get a new one as you're otherwise stuck in a neverending shit hole.

Eg. I mostly leave when I have the feeling that either I cannot learn anything anymore (for whatever reasons) or that I'm not getting the support / respect I need.

Everything else is negotiable. Support / respect from those I directly work with or are "above" me. As I'm mostly involved in management, a mutiny of the peasants eh underlings eh developers is the thing you expect daily ;)