You're not sleeping well. You're second-guessing every PR you open. You've started rehearsing what to say before every Slack message, just in case it gets used against you later. You tell yourself it'll get better: you just need to work harder, get faster, prove yourself.
It doesn't get better.
I almost left the industry because of one job
I was a few years into my career when I landed at a company that looked great on paper. The stack was interesting, the product was ambitious, and the team seemed senior.
What I didn't see until I was inside it: micromanagement at every level, constant peer comparison, and a culture where asking questions felt dangerous. My confidence eroded fast. I started overstudying at night to compensate — trying to out-skill the anxiety. I isolated. I second-guessed things I'd done confidently six months earlier.
I nearly walked away from development entirely. Not because I wasn't good enough, but because the environment was making me into someone I didn't recognize.
What changed wasn't my effort level: it was leaving.
The thing nobody tells you about toxic workplaces
We talk a lot about hard work, resilience, and "just pushing through." Like it's a badge of honor within the development world. What we talk about less: a bad environment doesn't just slow your growth: it actively reverses it.
Psychological safety isn't a buzzword. It's the condition under which learning actually happens. When you're afraid to ask questions, you stop asking them. When you're afraid to make mistakes, you stop taking the kind of risks that lead to real skill. When you're constantly compared to peers, you optimize for looking capable instead of actually becoming capable.
The reframe that changed how I think about this: the environment you work in is a variable, not a fixed condition. You can leave. Sure, perhaps not immediately because a family depends on you and you need to pay rent, but ultimately.
I've mentored developers who spent two or three years grinding harder in a bad workplace, convinced that their discomfort meant they needed to grow more. Some of them did grow: in spite of the environment, not because of it. All of them would have grown faster somewhere else.
Green flags worth protecting
After leaving that job, I became deliberate about what a good environment actually looks like in practice. Here's what I watch for:
Senior devs who answer questions without making you feel small. This sounds like a low bar, but it isn't. When you work somewhere this is normal, your learning rate doubles.
Code reviews focused on architecture and readability, not on who wrote it. Feedback that's attached to the code, not to you as a person.
Mistakes handled with curiosity, not punishment. The first time something breaks in production and your lead says "okay, what happened and what do we fix" — that's data. Stay.
People who admit they don't know things. On high-functioning teams, "I'm not sure, let me check" is standard. It signals that ego isn't running the technical decision-making.
Onboarding that assumes you're capable. Not hand-holding, not sink-or-swim — actual structure that respects your time.
Red flags to take seriously
No documentation and nobody has time to explain things. This means context is hoarded, not shared.
Interviews that emphasize how "fast-paced" everything is, but can't describe what good work looks like.
Senior devs who compete instead of collaborate. Seniority shouldn't come with contempt for the people coming up behind you.
Feedback that's vague and personal. "You need to be more proactive" with no specifics is a sign that psychological safety is low: no one wants to give you real information but they do expect a lot from you.
Being made to feel lucky to be there. If you're hearing that implicitly or explicitly: leave. That framing exists to prevent you from advocating for yourself.
When to actually go
Three months of trying to change your environment with no movement. That's a reasonable window. If you've raised concerns, adjusted your approach, tried to find allies (and the conditions haven't shifted) the conditions won't shift.
When the job is changing who you are off the clock. If you're more anxious, more defensive, less curious than you were a year ago.
Your first job isn't your final destination. Neither is your second or your third. The developers I've seen grow fastest weren't the ones who endured the most: they were the ones who found environments where growth was actually possible, and stayed long enough to take advantage of it.
A bad environment doesn't mean you're bad at this. It means you're in the wrong place.
Your effort matters, sure, but effort compounds when the conditions support it and stalls when they don't. The bravest thing I did early in my career wasn't staying and grinding. It was recognizing the difference.
Have you ever stayed somewhere longer than you should have? What finally made you go or what made you realize you'd found the right place?
If this resonates, a lot of what I learned navigating bad environments, and building better ones, is in my book From Hello World to Team Lead, a practical guide for developers who want to grow without losing themselves in the process. And if you're currently in a situation that feels stuck and want to talk it through, you can book a developer growth session with me.
Top comments (0)