有毒な職場が私の開発者キャリアから離脱を迫った

よく眠れなかった。PR を開くたびに再考していた。Slack での発言を、後で悪用されないように事前に練習していた。状況が良くなるとは思っていた：努力すれば、速く働き、自己を証明すればいいからだ。だがそれはなかった。私のキャリアが数年に入ってから、紙の上では素晴らしい企業に雇われた。スタックは興味深い、製品は野心に満ち、チームも上級者らしい。しかし、私が内部に入ってから初めて気づいたのは、あらゆるレベルでの微管理、絶え間ない同僚間の比較、質問をしてくることに危険を感じさせる文化だった。私の自信は急速に崩れた。夜、過度に勉強し、その不安をスキルアップで相殺しようとした。孤立して、6 か月前も自信を持ってやったことを疑い始めた。私は開発から完全に離れることを考えた。それが十分じゃないからではなく、環境が私を認めない自分自身に作り変えていたからだ。変われたのは努力ではなく、去ったことだった。私たちは多くの場合、過剰な努力、レジリエンス、そして「押し通すこと」について議論する。開発界でそれは栄誉の証に過ぎない。あまり語らないのは、悪い環境は単に成長を遅らせるだけでなく、能動的にそれを逆転する点だ。心理的安全性はスローガンではない。それは学習が実際に起こる条件だ。質問を恐れるなら、あなたは質問を止める。ミスをして恐れるなら、現実のスキルを導くようなリスクを止める。絶えず同僚と比較されるなら、あなたは実際に能力を身につけるのではなく、能力に見えているように最適化する。私の思考を変えた再定義：あなたが仕事をする環境は、固定された条件ではなく変数だ。あなたは去れる。もちろん、家族に依存して家賃を払う必要があるため、すぐにではないかもしれないが、最終的には。私は、悪い職場で 2 か年、3 か年、より努力を続けていた、彼らの不快感は成長する必要があることを信じていた開発者をメンターしてきた。いくつかは成長した：環境にもかかわらず、それ故ではなく。他のどこかで、彼らはより速く成長したであろう。その仕事から退いた後、私は良い環境が実際にどう見えるべきか、より意図的になった。私が監視するのは、以下のような点だ：質問に答えながらあなたを小さく感じさせない上級開発者。これは低いハードルに聞こえるが、それはそうではない。この環境で働くとき、あなたの学習率は倍になる。建築や読みやすさに焦点を当てたコードレビュー、そしてそれが誰によって書かれたかではない。あなたの人格に添わっていない、コードに添わついたフィードバック。ミスを罰ではなく、好奇心を持って扱うこと。何かproduction で崩れた最初の回で、リーダーが「おけ、何が起きたか、どう修正するか」时说たら——それはデータだ。残れ。自分も知らないことを認める人々。高度に機能するチームでは、「私はわからない、調べてみよう」は標準だ。それはエゴが技術的决定を支配していないことを示唆する。あなたが能力があると想定したオンボーディング。ハンドヘルドも、シンク・オブ・スイムでもない。あなたの時間を尊重する実際の構造だ。ドキュメントがなく、誰かがものを説明する時間もない。これは文脈が共有されず、独占されていることを意味する。すべてが速いというのを強調するが、良い仕事とはどう見えるかを説明できない面接。協力する代わりに競争する上級開発者。年齢は後ろの人々の軽蔑を伴うべきではない。「もっと能動的でなければ」と、具体性なしで言うフィードバック。これは心理的安全性が低いことのサインだ：誰もあなたに本当の情報を与えたくないが、あなたから多くを期待している。その場に在ることが幸運だと感じるようにさせること。それは明示的または黙認で聞くなら、去れ。それはあなたの自己弁護を阻止するために存在する。環境を変えようとした 3 か月の努力に動きなし。それは妥当な期間だ。懸念を提起し、アプローチを調整し、連帯を探すことを試みて (かつ条件は変化しなかった) なら、条件は変化しない。その仕事は、あなたを変え続ける中での、

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 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. 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. 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. 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. 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.