Why I Like Working on Multiple Freelance Projects at Once

One thing I often do: take on more than one freelance project at a time, rather than focusing on a single client. To some people that sounds exhausting, but for me there are some real benefits.

Variety keeps skills sharp. A desktop tools project (Avalonia, Go) needs a very different skillset from a mobile app project (Swift/Kotlin) or an internal web app (React/Spring Boot). Switching contexts like this keeps me from getting stuck on just one type of problem.

Not putting all eggs in one basket. If one project is quiet for a stretch (waiting on client approval, or in a testing phase, say), other projects keep moving. That makes the overall work rhythm more stable than depending on a single source of work.

Side projects become a space to experiment. Things I learn from one project (like the no-backend architecture in Istiqomah) often get reused in another. Project variety makes my “experience library” richer.

The challenges are real too: it needs tighter time management, clear communication with each client about timeline expectations, and a context-switching ability that has to be constantly practiced.

The key for me: don’t take on more than I can deliver with consistent quality. Better to run two or three projects well than many projects done half-heartedly.