Also, changing a job is two-side process. they need to like you and you need to like them. If you find that too many developers are going out, too many job offers from their side, that might mean that the company is toxic. Stable good companies, don't have a lot of job offers. They are not so aggressive searching for people ;)
Always ask why they hire, try to find out why people leave.
this sounds like a hiring problem, not a you problem. Companies with no docs and no senior expecting you to match output in 2 months are setting you up to fail.
the rabbit hole thing isnt a bug. Understanding the system before shipping is good engineering. The wrong companies just call it "slow".
My recommendation is to look at game companies. Those jobs are fewer, harder to get, sometimes pay more but usually less, and the work tends to be much harder. You will be writing code though. Game companies
Otherwise look towards jobs that require niche, less popular, languages or tend to require additional skills like an engineering, law, or medical background.
The ultimate goal is to find a work culture that values selflessness. Whether that means operations, product quality, or original problems to solve. When you are surrounded by self oriented people you will always get firefighting: that kind of environment where everything is an emergency and everything is tech debt and the primary goal is worship of some tool because all that matters is the tool user (the developers own desires) as opposed to the product users, the actual business target.
A lot of what you talk about is just the bread and butter of software at BigCo, especially at a senior level. Unrealistic expectations, undocumented code, some firefighting, etc. are all just par for the course, and you need to have ways of dealing with that, staying cool and grounded, not letting it get to you, and not letting it stop you from showing some delivered results each week.
Figuring out, details, debugging, etc... yes, these need to happen, but you have to slot those in around delivering things, often without a complete picture.
What are the sizes of the companies you’ve been working at? I much prefer and recommend small teams, those where you have interacted with every other person. And I do mean every person, not every developer.
Consider medical device software. Often embedded C code, needs to be rigorously documented and tested, has longer development cycles, and certainly no attitudes of "bugs are fine, ship it and we'll patch later."
Banking software. No place to hurry there.
Also, changing a job is two-side process. they need to like you and you need to like them. If you find that too many developers are going out, too many job offers from their side, that might mean that the company is toxic. Stable good companies, don't have a lot of job offers. They are not so aggressive searching for people ;)
Always ask why they hire, try to find out why people leave.
Does Medicine also work?
this sounds like a hiring problem, not a you problem. Companies with no docs and no senior expecting you to match output in 2 months are setting you up to fail.
the rabbit hole thing isnt a bug. Understanding the system before shipping is good engineering. The wrong companies just call it "slow".
My recommendation is to look at game companies. Those jobs are fewer, harder to get, sometimes pay more but usually less, and the work tends to be much harder. You will be writing code though. Game companies
Otherwise look towards jobs that require niche, less popular, languages or tend to require additional skills like an engineering, law, or medical background.
The ultimate goal is to find a work culture that values selflessness. Whether that means operations, product quality, or original problems to solve. When you are surrounded by self oriented people you will always get firefighting: that kind of environment where everything is an emergency and everything is tech debt and the primary goal is worship of some tool because all that matters is the tool user (the developers own desires) as opposed to the product users, the actual business target.
A lot of what you talk about is just the bread and butter of software at BigCo, especially at a senior level. Unrealistic expectations, undocumented code, some firefighting, etc. are all just par for the course, and you need to have ways of dealing with that, staying cool and grounded, not letting it get to you, and not letting it stop you from showing some delivered results each week.
Figuring out, details, debugging, etc... yes, these need to happen, but you have to slot those in around delivering things, often without a complete picture.
What are the sizes of the companies you’ve been working at? I much prefer and recommend small teams, those where you have interacted with every other person. And I do mean every person, not every developer.
Consider medical device software. Often embedded C code, needs to be rigorously documented and tested, has longer development cycles, and certainly no attitudes of "bugs are fine, ship it and we'll patch later."