There’s a specific kind of awful that happens when you open your editor and feel nothing.
Not frustration. Not tiredness. Just… nothing. The blank cursor blinking at you, and the quiet realization that the thing you used to do at 2am because you wanted to — the thing you probably listed as a hobby in the same breath as a job — has gone cold.
For a lot of us, that moment doesn’t feel like work stress. It feels like loss. And I think that’s exactly what it is.
It feels like grief because it kind of is
When we think about burnout, we usually reach for the language of exhaustion. And exhaustion is real — it’s one of the three core dimensions that Christina Maslach’s foundational research identified when she mapped out what burnout actually looks like. But alongside exhaustion, her model also describes cynicism — a gradual detachment and loss of idealism toward the work itself — and a reduced sense of personal efficacy, the creeping feeling that you’re no longer good at or connected to what you do. (Maslach, 2016, World Psychiatry)
That second and third dimension are where passion goes missing. And it’s not a clean, obvious switch. The research describes burnout as a sequential process: exhaustion comes first, then as a kind of coping mechanism, you start to pull back emotionally from the work. Cynicism — that flat, detached feeling — is actually your mind trying to protect itself. (Frontiers in Organizational Psychology, 2025) The problem is it takes the joy with it on the way out.
Psychologists describe grief as the response to losing something that was central to the self — and the more central that thing was, the harder the impact. (EBSCO Research Starters: Grieving in Psychopathology) For a lot of developers, coding isn’t peripheral. It’s identity-level. So when the warmth drains out of it, the feelings that follow — the confusion, the numbness, the sense of something missing that you can’t quite name — they’re not dramatic or overblown. They make complete sense.
What research says about how burnout picks apart intrinsic motivation
Most of us got into development because of intrinsic motivation — that internal drive that comes from curiosity, the satisfaction of solving something, the pleasure of making a thing work. It’s not about salary or status. It’s the pull of the problem itself.
Self-Determination Theory, developed by Deci and Ryan, argues that intrinsic motivation depends on three basic psychological needs being met: autonomy (feeling like you’re choosing your work, not just executing orders), competence (feeling effective and capable), and relatedness (feeling connected to people and to something meaningful). When those needs are supported, people are more self-motivated, more satisfied, and more resilient. When they’re thwarted — by overload, micromanagement, isolation, or grinding pressure — motivation deteriorates. (Ryan & Deci, 2000, American Psychologist)
Burnout is, in many ways, the accumulated result of those needs being crushed. Research consistently finds that intrinsic motivation and burnout are inversely related — higher burnout correlates with lower intrinsic motivation, and vice versa. (Kim, 2018, via ResearchGate) What makes this especially painful is that the people most likely to burn out are often the ones who started with the most intrinsic motivation. The ones who cared the most. Who worked the longest hours because they genuinely wanted to. Burnout didn’t take something small from them — it reached in and took the thing that mattered most.
The identity problem
Here’s where it gets harder. For a lot of people in this community, “developer” isn’t just a job title. It’s a core part of how you understand yourself. Maybe you’ve been coding since you were a teenager. Maybe you built your social world around it, took pride in it, defined your competence through it.
A Pew Research survey found that over half of postgraduate workers consider their jobs central to their overall identity. For developers who came up in a culture that celebrates the craftsperson, the tinkerer, the person who does this stuff for fun — that number is probably higher.
Psychologists describe identity coherence as the stable story we tell about who we are. When the thing at the center of that story stops feeling like yours — when you sit down to code and feel detached from it, or actively dread it — that coherence can start to crack. Research on professional identity crises describes the experience as involving “feelings of dissociation, depression, grief, disorientation, and denial.” (More Than My Title) That’s not melodrama. That’s an accurate description of what it’s like when your sense of self loses its anchor.
James Marcia’s research on identity development showed how early commitments — “I am an engineer,” “I am a builder” — provide stability, but also rigidity. When the environment changes faster than the self-concept can adapt, coherence fails. (Psychology Today) The person doesn’t just lose interest in their work. They lose a piece of their story about who they are. That’s why it can feel so much bigger than “I need a holiday.”
Does the passion come back?
This is the question underneath everything, and I want to be honest with you: the research doesn’t give a single clean answer.
What it does say is encouraging, if cautious. Burnout is not a permanent state. The process that produces it — chronic stress eroding your psychological needs — is in principle reversible when the conditions change. (Psyche Guides, 2025) Recovery is real. People do come back to their work and find something waiting for them.
But there’s a distinction worth sitting with, from the research on passion itself. Vallerand’s Dualistic Model of Passion separates harmonious passion — where you engage with work because you genuinely love it, and it sits alongside the rest of your life — from obsessive passion, where the activity controls you, your self-worth is contingent on it, and rest feels impossible. Research consistently finds that harmonious passion protects against burnout, while obsessive passion can actually feed it. (MDPI Sustainability, 2025)
The uncomfortable implication: sometimes what “comes back” after burnout isn’t exactly the same thing that existed before. The frantic, all-consuming drive that some of us used to feel — the kind that made us lose track of time in a good way, but also the kind that made us ignore sleep and relationships and the warning signs — that version may not return, or not return in the same form. And honestly? That might be okay. A healthier relationship with the work, even if it’s quieter, might be worth more in the long run than rekindling an obsession.
What the research points toward for recovery: rebuilding the conditions where intrinsic motivation can exist again — small doses of autonomy, moments of genuine competence, connection to other people doing meaningful things. (Ryan & Deci, American Psychologist)
Some gentle ways to find your way back (or find something new)
None of this is prescriptive. We’re all in different places. But these are directions the research and a lot of anecdotal experience point toward:
Give yourself permission to not feel it right now. Trying to force enthusiasm when the tank is empty tends to make things worse. The RescueTime burnout series notes that meaningful reconnection usually requires some real distance first — not a weekend, sometimes much longer.
Look for the smallest version of the thing you used to love. Not a side project. Not a hackathon. Maybe just a tiny script that does something you find interesting, with no stakes and no one watching. The goal isn’t to recapture the old feeling — it’s to find out if a smaller, quieter version of it is still in there somewhere.
Separate your identity from the outcome. This is easier said than done, but the research on identity crisis suggests that developing a sense of self that exists outside your work makes you more resilient, not less committed. (Allwork.space, 2025) You were a person before you were a developer.
Let yourself mourn. If you’ve lost something real — the feeling of flow, the love of the craft, the sense that this work means something — then grief is an appropriate response to that loss. You don’t need to rush past it or reframe it into a growth opportunity.
Consider whether the relationship with the work needs to change, not just recover. For some people, the path through isn’t back to exactly where they were — it’s toward a different relationship with the work entirely. A changed relationship isn’t a failed recovery. It might be a more honest one.
—
For those of us whose whole identity got wrapped up in being the person who loves this — the grief of losing that love is real, and it deserves to be taken seriously. Not fixed immediately. Not optimized. Just acknowledged.
—
Over to you: If you’ve been through this — the moment when coding stopped feeling like something you wanted to do — what did that feel like for you? And if you found your way back (or found something else), what shifted?
No pressure to have a tidy answer. This space is for the messy ones too.
