Should you juggle between multiple game dev projects?

I think the majority of indie devs juggle multiple projects, and for good reason. I want to talk about whether this approach is beneficial or not. You often hear people saying you should focus on one thing at a time, but I believe that what's right for one person isn't necessarily right for another. Humans are naturally inclined towards multitasking, not in the sense of doing two things simultaneously, but in the sense of breaking up your day to work on different things. You might spend a couple of hours on one project, then switch to another for a bit, and so on.


First, let’s look at the issue of starting too many projects and how it might impact your ability to actually finish a game. A common trap is starting something new, working on it for a few weeks or months, then dropping it for a shiny new idea. I’ll admit, this has happened to me occasionally, but usually for reasons not related to the allure of a new project—sometimes life just gets in the way, and you have to reduce your workload. What I’m talking about here are the cases where a developer constantly starts something new because the next idea seems more exciting. Before you know it, you’ve got a backlog of half-finished projects, none of which are close to completion. I’ve struggled with this while writing books too. You need to be consistent, especially if you're writing a series, but you get halfway through and start a new book instead. The same applies to game development: if you keep starting new projects, you probably won’t finish any. That’s okay if you’re doing it as a hobby, but if you’re serious about being a professional developer, you need to commit to what you start.

While developing Parallel Pulse, I'm also developing my new horror themed game called: Cook or be Cooked.

On the flip side, juggling multiple projects can actually be beneficial. Humans get bored, and working on the same project day in, day out, can lead to burnout. Not everyone deals with this, but in my case, working on two or three projects at a time has been helpful. It keeps things fresh, helps you learn new things, and gives you a creative break from focusing on just one game. This has been especially motivating for me, particularly when collaborating with a team. For my personal projects, I try to keep the scope limited and aim to finish smaller projects. Whether it’s a commercial release in six months or a quick game jam in a month, completing something small gives a sense of accomplishment and keeps the motivation up.


The key here is knowing your limits. I’ve learned over time not to exceed them, because that’s when things start to go wrong. In the end, there’s no one-size-fits-all answer to whether you should juggle multiple projects. It’s all about finding what works best for you and your workflow.

Comments

Post a Comment

Popular posts from this blog

Painful Cuts I Had to Make to My Game

Image
 As much as we hate them, cuts in game development are often necessary. If I’m being honest, I’ve never worked on a project where we didn’t have to make some tough decisions. You start with bigger aspirations—dozens of sprites, backgrounds, and CGs—only to realize that everything takes an insane amount of time and resources. Parallel Pulse was no different. The original vision for the game was something akin to TWEWY in terms of combat, but with a narrative more aligned with the Persona series, where you bond and hang out with friends. The game started as an action RPG, and until mid-May, I was set on this approach. But then reality hit—with each sprite taking way more than what I had initially thought it'd take. In a previous devlog, I gave you a glimpse of how much effort goes into creating a single sprite sheet. It goes without saying that this became a nightmare for me—and not just for the main character but for each enemy as well. Every enemy needed at least three animations, ...
Read more

Why I’m Participating in This Year’s Spooktober Jam

Image
  Before I explain why I made this decision, let me give you some context about last year’s Spooktober Jam. Participating in this jam has become a tradition for me—this will be my fourth time taking part. However, this time around, I’ll be taking on a different role. While I’ll still lead the project, I won’t be handling the programming. Since I don’t have much experience with the Godot engine, I’ll focus on what I’m best at: production and narrative design. The idea for the narrative of this game came to me last year, right after finishing our entry for the previous Spooktober Jam. I thought, “What if we did a twisted version of the classic fairy tale Hansel and Gretel, but with a humorous twist similar to  The Addams Family ?" And that's when the idea for  Cook or Be Cooked  was born. At first, I shelved the idea because I had other projects and personal matters to focus on, but the concept kept resurfacing in my mind—how the story should unfold and how the visuals...
Read more