DEV Community

Cover image for I Had a Full-Time Job, Freelance Clients and Five Side Projects. So I Stopped Before I Burned Out
Roman Popovych
Roman Popovych

Posted on

I Had a Full-Time Job, Freelance Clients and Five Side Projects. So I Stopped Before I Burned Out

I haven't posted anything for a while, and the reason is not very glamorous: my attention fell apart.

I work full-time as a full-stack developer at a fintech company. On top of that, my girlfriend and I have been freelancing for about three years, and together we have completed more than 50 orders. And on top of that, I kept starting side projects. Not finishing them. Starting them.

At some point I noticed a pattern. I would open a project, work on it for a few evenings, get an idea for something else and switch. The old project stayed half-done, in a browser tab and somewhere in the back of my head. Every new idea felt like relief. Every old one felt like a small debt.

I'm not writing this as someone who "beat burnout". I'm writing it from the middle. I could feel it coming, so I decided to stop before it arrived.

What it looked like from the inside

There was no dramatic moment. No crash, no breakdown. My week simply had three layers:

  • the main job during the day;
  • freelance work in the evenings;
  • side projects whenever there was "time left", which in practice meant late nights and weekends.

The problem was not the amount of work by itself. It was that nothing ever closed. I had five open loops, and each of them asked for attention at the same time. When you switch between five things, you don't do five things. You do five beginnings.

Step 1: I took days off from my main job

The first thing I did was take a few days off at my main job.

It felt strange to step away from the one part of my life that was actually going fine. But that was the point. As long as I was switching between work, clients and side projects every few hours, I couldn't see the whole picture. I needed a few days where I wasn't reacting to anything, just to look at everything from the outside and decide.

Step 2: An honest inventory

I wrote down every side project and gave each one a single honest status. Not "in progress", because everything is always "in progress". A real status:

  • devtools.abect.com: finished. Free browser-based developer tools: image converters, favicon and meta tag generators, code converters. I started it in April after one too many converter sites full of casino ads. It now lives on its own, and I'm not planning new features.
  • agency.abect.com: almost finished. The site of our small studio. The main part was finished the day before I wrote this; a few fixes are left.
  • abect.com: frozen. A simple website builder.
  • finddax.com: waiting. It finds local businesses without a website on Google Maps. It waits for Abect, because the plan is to connect the two.
  • terraristy.com: being tested. Gaming news and Steam deals. We restructured it recently and are now watching whether it starts bringing search traffic.

Writing it down did two things.

First, it turned a vague feeling of "I have too much" into a short list. Five lines are scary in your head and surprisingly manageable on paper.

Second, it showed the dependencies. Finddax can't really move until Abect does, because the whole idea is that Finddax finds a business and Abect builds its site. That means every evening I spent on Finddax before Abect was ready was an evening spent on the wrong thing. I only saw that once the list was in front of me.

Step 3: Pick two. Freeze the rest. Don't kill anything

My goal until the end of November is simple: finish the agency site and Terraristy. Everything else waits.

Why these two? They are the closest to done. The agency site can also bring paid work, which buys time for everything else. Terraristy has already been restructured, so it mostly needs time and attention, not a rewrite.

Why freeze instead of deleting? For me, killing a project feels like a failure, so I keep thinking about it anyway. Freezing is a decision: this project is not dead, it's just not now. It has a place in the queue, and that is enough to stop it from tugging at me every evening.

Step 4: Stop doing everything alone

This was the biggest change.

For a long time I did most of the building myself. That works when you have one project. It doesn't work when you have five plus a job plus clients.

So I asked for help:

  • My friend Roman joined to help with development. He built the front end of the new agency site.
  • Dayana Melay designed the new version of the site.
  • My girlfriend is launching ads for the agency site, and together we will look for new development orders.

The obvious benefit is less work on my plate. The less obvious one surprised me more: other people create real deadlines. When it's only you, "I'll finish it next week" can repeat forever. When a friend has already built the layout and someone is waiting to launch ads, the project has to move.

A small detour about AI

The very first version of the agency site was generated by AI. It looked terrible.

I use AI tools a lot, and they are great at getting something on the screen fast. But "something on the screen" is not a finished product. The jump from that first version to a site we are not embarrassed to show took a real designer and a real developer. I keep relearning the same lesson: AI speeds up the start, not the finish.

Step 5: Make progress visible

Before the redesign I saved the starting metrics of the agency site. From now on I'll share what we change and what happens to the numbers, good or bad.

The plan for the next one or two work sessions:

  • speed up page loading;
  • add a price calculator widget so a client can estimate the cost of a site on their own;
  • publish two blog posts a week for the next two months.

Writing progress down in public is not about looking productive. It's a way to stay honest. A goal that only lives in my head moves every week. A goal I've posted with a date and a baseline is much harder to quietly forget.

What helped me, in short

This is not a universal method, just what I'm doing right now:

  1. Step back for a few days. You can't sort your priorities while you are switching between them every hour.
  2. Give every project one honest status. Finished, almost finished, frozen, waiting, testing. No "in progress".
  3. Look for dependencies. Some projects can't move until another one does. Work on those first.
  4. Pick two and freeze the rest. Frozen is not dead. It just isn't now.
  5. Ask for help. Other people bring skills you don't have and deadlines you can't postpone.
  6. Make progress visible. Save the baseline, then show what changed.

One honest note: I caught this early, while it was still a feeling that burnout was coming. If it's already more than a feeling for you, if you've been dreading opening your laptop for weeks, a list of projects won't fix it. Talk to someone you trust, and consider talking to a professional.

What's next

At the end of November I'll come back and report whether I actually closed both projects, with the numbers.

Until then, I'm curious: how many unfinished side projects do you have right now? Be honest.

Top comments (0)