What're the reasons that made you quit your developer jobs?

@sqlkid Lovee your reply, thank you

@rutee07 spaghetti codebase is absolutely nightmare.

But management wouldn't careless. They demand the job done within deadline. That is the sick part we all dev had to face.

I left before due to family commitments. I am thinking of leaving now because I am mainly demoralized from lots of co-workers that left already due to poor management (lack of salary increase, no promotion, less benefits etc) and we end up getting new hires which had to be taught which feels like starting again anyway.

Management straight up lied to employees

Its always management

Micromanagement.
It's about the only thing I've actually walked out for.

Codebases suck, but jumping ship doesn't guarantee you'll be going somewhere better in the regard.

@iamai its much easier to hire fresh grads rather than to appeal to experieced devs

@C0D4 i would like to ask what type of micromanagement are you experiencing

I wanted to do my degree with computing.

But after experience what is like to be working as a dev in the industry.

That feeling to continue studying really fade.

I always try and make sure it's better opportunity elsewhere, rather than frustration where I currently am, that causes me to move.

In my case most recently (I'm serving out my notice now) because I had a very good offer from elsewhere, with better career progression opportunities, greenfield development (always a plus), a dedicated development role rather than one with support / maintenance / management bundled in, more holiday, and a compensation package close to twice my current one.

Spaghetti code ported from C to C++, with a manager that was very reluctant on refactoring because we never had budget. There were more memory leaks in the software than sand particles on a beach. As a result nothing got ever delivered on time. I've heard stories of the manager practicing mushroom management as well, but that was before I started working there.

I enjoy screwing around in legacy code, but I am not going to keep trying to keep my head above water because dry land is not within the budget. ffs.

Better offers :)

Because idiots

@DevRage a previous job now.

But every decision that needed to be made had to be made with management, Regardless of what it was. It became so time consuming and the lack of freedom to just get on with the work got the better of me.

That and the 12-16 hour days, and expectations to read emails past 11pm at night, in the end I quit due to a client throwing blame on a half completed change that they delayed and never confirmed that it could be finished.

Now I work with some chaotic projects and spaghetti code and 0 tests, and before you say "make tests", that would require some heavy duty refactoring (think rewrite level) some days I want to just burn them, but from a management level, I don't have to deal with 90% of the bullshit, although I'm actively engaging them.

You can't pick your projects, but you sure as hell can pick your workplace.

Not a developer job in my case. I was a first-line helpdesk + Linux engineer person.

I loved the environment and the company but at some point the helpdesk drove me crazy.

Now I'm happily working as a cybersecurity engineer!

Exploitation.
I just couldn't take it anymore. I think it was my fault only to take a job at a startup.

I was giving more than 19 hours to the job (10 hrs + 4hrs of travel + 5 hours of guilt study at home). Yet i was constantly being called up in meetings and being questioned on my skills.

They were like, "this is the design of our idea. Built the complete app out of it (plausible demand since am the Android dev intern) . Also figure out the structure of cloud db(wtf?) , and if you are in any confusion, you can ask the senior devs (okay i guess?) . Also complete this in x days(x= very impractical no.) "

I never thought designing a cloud db would be my area of work .The only good thing in the above equation was the support of senior devs, but that also turned out to be hoax. The devs were "busy" and i had to figure out on my own. And if i couldn't do it, then back to questioning of my skills :/

I was so mentally broken up, that i left the next day i got my salary

@StopWastingTime

That is so true. When i first started off with my career. I'm promised that there will be senior to help me out.

But turn out they will and will always be busy. I manage to dig the code and search for reference.

That was how i manage to survive. But eventually i burnout by crazy demands from a mean direct supervisor.

It's not just start-up. Where i am at is in a MNC. But i believe start-up is way rush. But meeting a nassicsist is nasty.

StopWastingTime, that's my experience in consulting too. Can't wait to GTFO.

The chair was not comfortable

I wasn't allowed to use my phone even after work is completed. Even their Internet connection was fucking slow. Whenever I complained about that, Seniors forced me to use my own mobile internet connection. Rules were so strict for juniors.

@someguyintheus I'm also in consulting.