How to start a side project when you're still recovering from burnout

The first thing well-meaning people say when they hear you've taken time off is some version of: "Are you keeping your skills sharp? Building anything?" The question arrives with good intentions and lands like a small stone in a pond you were trying to keep still. Because the reason you're taking time off is that you ran yourself into the ground building things, and the suggestion that recovery might involve more building is, if you're honest, difficult to receive.

But there is a version of it that's right. Not the version where you treat your leave as a productivity window. Not the version where you build something impressive to explain the gap in your CV. A different version — smaller, quieter, less legible to anyone watching from outside. Here's how to tell the difference, and how to get there from wherever you currently are.

Why the standard advice gets this wrong

The conventional wisdom about side projects during career gaps was built for people who are bored or restless, not for people who are recovering from burnout. It assumes a baseline of mental energy, motivation, and executive function that burnout specifically depletes. It assumes you can set goals and hold them. It assumes you can sit with a hard problem long enough to push through it. These are the capacities that burnout removes — and treating their absence as a motivation problem you can think your way out of is how people extend their recovery by months.

Burnout isn't a productivity failure. It's a physiological state. Your nervous system is dysregulated. Your stress hormones are running on reserves. Your capacity for sustained attention — the kind that meaningful technical work requires — is substantially reduced. This is the expected outcome of prolonged high-performance under chronic stress, not a personal failing. Starting a demanding side project during acute recovery is roughly analogous to starting intensive training with a stress fracture. You can do it. It won't help.

The core mistake in the "stay sharp" framing is conflating two distinct processes: technical skill maintenance and psychological recovery. They don't happen on the same timeline. Your technical skills won't meaningfully atrophy in three months. Your nervous system needs considerably longer to return to baseline. Optimising for the former at the expense of the latter is not a good trade, even when it feels like one.

What readiness actually feels like

One of the harder things about burnout recovery is that the markers of readiness are slippery. You might be waiting for a specific feeling — a morning where you wake up and think: I want to make something. That moment sometimes comes. More often, readiness arrives less dramatically.

What it typically looks like is a small pull toward something. Not drive, not motivation in the conventional sense — curiosity. An article about a technology you find interesting, and the thought: I'd like to try that. A problem you encounter in your own life, and a half-formed idea of a solution. These small tugs are easy to dismiss when you're used to a version of motivation that felt more like compulsion. They're worth paying attention to.

If you're waiting for the energy to feel like it did before the burnout, you may wait for a long time. The pre-burnout state often included a driven quality that wasn't entirely healthy — a compulsive productivity that felt like strength and turned out to be a significant part of the problem. The readiness that emerges in recovery tends to be quieter, and recognising it as enough requires recalibrating what "wanting to work" actually means for you.

A practical test: can you sit with an interesting problem for twenty minutes without it feeling like a physical burden? Not an important problem — any problem. A puzzle, a curiosity, something with no stakes at all. If the answer is yes on some days, intermittently, that's probably enough to start small.

What kind of project actually works

The most important characteristic of a recovery-compatible side project is that it has no stakes. Not low stakes — no stakes. Nobody is waiting for it. It does nothing useful for your career. If you abandon it tomorrow, no one will know. This is exactly what makes it useful.

High-stakes projects — things with audiences, things that could become something, things you might show in an interview — carry with them all the anxiety and performance pressure that burnout was partly produced by. Your nervous system cannot reliably distinguish between "stakes that matter" and "stakes I've invented." It responds to the psychological weight of importance regardless of whether that importance is externally real. A side project you're building to prove something is a job you're doing for free.

What tends to work during recovery is something that engages your curiosity without engaging your identity. A small script that automates something you find annoying. A tool that solves a problem only you have, that nobody else needs to care about. A creative project that uses technical skills in a way that doesn't feel like technical work — something generative, something visual, something that prioritises interestingness over usefulness.

Some questions that help find the right shape for this:

What did you find interesting in tech before it became your job? There's often something there — the original curiosity that drew you in before the industry optimised it into a career track. Procedural generation, weird algorithms, language processing, graphics, building small tools that did one thing well. Whatever it was, it's probably still accessible somewhere beneath the layers of professional obligation.

Is there a problem in your actual life that a small technical solution would marginally improve? Not an app idea, not something with a market — a small, personal, un-monetisable solution to an inconvenience that only you experience. These work well because the only person whose opinion of the outcome matters is yours.

Is there a technology you're curious about with no particular career relevance? Learning something purely because it interests you is specifically good for recovery because it removes the instrumental framing from the activity. You're not building skills for the next role. You're just interested in how it works.

How to protect the project from your old habits

The biggest risk with starting a side project during recovery isn't failing to start. It's importing your pre-burnout work habits into it and turning it back into a source of stress. This happens faster than you'd expect, and the shift is subtle enough that you often don't notice it until you're already feeling the familiar weight.

The patterns to watch for: setting deadlines you don't need. Building infrastructure for a project that has no users — the test suite, the CI pipeline, the Docker setup for something you run locally on your own machine. Feeling guilty when you haven't touched it for three days. Comparing what you're building to what someone with more energy would build. Thinking about how you'd explain it in an interview before you've written ten lines of code.

These aren't character flaws. They're habits that were reinforced over years in high-performance environments, and they will arrive automatically when you're doing something that looks like work. The project will take on the shape of your existing relationship with work unless you actively resist it.

The resistance is mostly about maintaining the condition of no stakes. No timelines. No output metrics. No announcements about what you're working on. Work on it when you feel like it, and stop when you stop feeling like it — including mid-session if that's what happens. This will be uncomfortable if your previous relationship with work involved sustained commitment and shipping things. That discomfort is the recovery process working. It isn't a sign something is wrong.

When the project starts to feel real

At some point in recovery, the small curiosity project may start to feel genuinely interesting — where you're choosing to spend time on it, where it develops its own internal logic, where you find yourself thinking about it between sessions in a way that feels energising rather than anxious. This is a good sign. It's worth paying attention to without immediately doing anything about it.

The question of whether to develop it into something more — whether to give it a name, whether to tell anyone about it, whether to expand its scope — is a question about your current capacity, not your ambition. Ambition tends to recover faster than capacity. The version of you that wants to do more can still be ahead of the version of you that can safely handle more. Staying honest about where that line actually is, rather than where you'd like it to be, is one of the ongoing tasks of recovery.

A useful self-check: has the project started to feel like a commitment rather than a choice? If yes, that's a sign you've crossed back into territory the recovery was supposed to be protecting you from. The shift can happen gradually — a small sense of obligation creeping in, a feeling that you should be further along than you are. If you notice it, the answer is almost always to reduce scope, not push through.

What this is actually for

The right side project during burnout recovery isn't proof that you still have it. It isn't preparation for what's next. It isn't an answer to the question about the gap in your CV — that question is less important than the people asking it imply, and you don't need to build your way out of it.

It's a reintroduction to the thing that probably drew you to this work in the first place — the part that existed before the performance, before the identity, before the sprint velocity and the quarterly planning cycles. The part that was just curiosity and the quiet satisfaction of making something do what you wanted it to do.

If you can find that again, even intermittently, you've found something worth protecting when you return to work. If you can't find it yet, that's useful information — not a verdict, just a reading of where you currently are. Give it more time. The curiosity doesn't go away. It just needs the noise to die down enough that it can be heard again.

If you're still working out whether you're genuinely recovering or just resting on the surface, the what actually helped me recover article is an honest account of what the timeline actually looked like — and what moved the needle and what didn't.