I remember my first year in the industry. I had a senior designer who took time to explain things—not just what to do, but why. Who reviewed my work with genuine feedback, not just approval or rejection. Who saw potential in me that I didn't see yet and invested in helping me grow into it.
That relationship was the difference between me staying in games and burning out like so many of my peers. And it's becoming increasingly rare. Mentorship in game development is dying, and with it, we're losing the infrastructure that turns junior talent into senior expertise.
Why Mentorship Is Disappearing
The reasons are structural. Crunch culture leaves no time for teaching—when you're working sixty-hour weeks to meet milestones, explaining your reasoning to a junior takes energy you don't have. Layoff cycles destroy continuity—mentors leave, relationships break, institutional knowledge walks out the door.
But there's also individual burnout among senior developers. After years of exploitation, many have nothing left to give. They've learned that mentorship isn't rewarded—promotions come from shipping features, not developing people. They've watched juniors they trained get laid off while they kept working.
The result is seniors who protect their energy, who do their work and go home, who see juniors as competitors for increasingly scarce positions rather than as future colleagues to invest in.
The Cost to Juniors
Without mentorship, junior developers struggle. They make mistakes that could have been avoided with guidance. They develop bad habits that become entrenched. They burn out trying to figure things out alone that seniors could explain in minutes.
More subtly, they miss the invisible curriculum—the norms, the shortcuts, the ways of thinking that aren't documented anywhere but get transmitted through working relationships. They enter the industry without understanding how it actually functions, making them vulnerable to exploitation they don't recognize.
The talent pipeline is clogged. Capable juniors leave because they're not supported, because they feel lost, because they can't see a path forward. The industry loses people it desperately needs.
The Cost to the Industry
Long-term, the mentorship crisis threatens the industry's creative capacity. Innovation requires institutional memory—understanding what has been tried, what failed, why. Without mentorship, each generation reinvents wheels poorly, unaware of prior solutions to problems they're struggling with.
Quality suffers when juniors can't learn from senior expertise. Codebases become unmaintainable. Design patterns become chaotic. Production processes become inefficient. The cumulative cost of not teaching is enormous, even if it doesn't show up on quarterly balance sheets.
What Would Help
Structural change is needed. Studios need to recognize mentorship as work worth rewarding—promotion criteria should include developing others, not just shipping features. Crunch reduction would create time for teaching. Stability would allow relationships to develop across projects.
But individuals can act too. Seniors can choose to invest in juniors even when it's not formally recognized. Juniors can seek mentors explicitly, ask for help, create relationships. Peer mentorship networks can fill gaps when institutional support is absent.
Professional organizations could do more—formal mentorship programs, resources for developing mentoring skills, recognition for mentors who invest in the next generation.
Conclusion
I'm still in touch with my first mentor. They're burned out now, working indie, trying to recover from decades of industry exploitation. But they changed my life, and through me, they've influenced dozens of developers I went on to mentor.
That's what's at stake in the mentorship crisis—not just individual careers, but the cumulative knowledge and culture of an entire industry. When we stop teaching, we start dying.
If you're senior: find someone to mentor. If you're junior: find someone to learn from. The system won't do this for us. We have to do it for each other.