How to Work on Games With a Full-Time Job

Most game developers start out making games around a full-time job, and many of the best indie games were built that way. It's entirely possible, but it requires a different approach than full-time development—one built on consistency, realistic scope, and a healthy relationship with the constraints rather than constant frustration at them.

Consistency beats intensity, especially with limited time

When game development gets only the hours left over after a job, the temptation is to wait for big free stretches—a weekend, a holiday—and try to make major progress in marathon sessions. This works far worse than steady small sessions, because marathons are rare, exhausting, and easily derailed by life, while a consistent habit of working a little most days compounds reliably. An hour in the evening, done regularly, adds up to a finished game; sporadic bursts of heroic effort usually don't, because they depend on conditions that rarely align. Building a sustainable rhythm that fits around your job, and protecting it, is the single most important habit for finishing a game alongside other commitments.

Scope to your actual available time, and reframe the job as an asset. The most common reason hobbyist projects die is being scoped as if the developer had full-time hours, which means they'd take a decade in reality and get abandoned long before. A project honestly sized to the few hours a week you actually have is one you can finish, and finishing a small game beats abandoning a large one every time. It also helps to see the day job clearly: it's not just an obstacle stealing your time, it's the thing removing financial pressure from your creative work, letting you make the game you want without it having to sell to pay rent. That freedom is valuable, and many developers who go full-time too early find their work gets worse under the pressure. Working on games around a job is a legitimate, proven path—the keys are consistency over intensity, scope matched to reality, and treating the job's stability as the foundation that lets you build without desperation.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

Small and finished beats big and abandoned

A folder of impressive unfinished projects teaches far less than a single small finished one, because finishing is where the hardest and most valuable lessons live — the unglamorous final stretch of bug-fixing, polishing, and shipping that ambitious abandoned projects never reach. Each completed game, however modest, builds the finishing muscle and the confidence that make the next one achievable.

So resist the pull of the dream project until you've shipped a few small ones. Scope to what you can actually complete, finish it, and let the experience of shipping make your bigger ambitions realistic.

Trust behaviour over opinions

People are unreliable narrators of their own experience — they're polite, they rationalise, they suggest fixes that miss the real problem. What they do tells the truth that what they say obscures: where they hesitate, where they get stuck, what they ignore, where they quit. The most valuable feedback is usually the behaviour you observe, not the opinion you're offered.

This is why watching beats asking, and why real data about what players actually do beats any amount of speculation. When several people stumble at the same spot, that's a problem worth fixing, regardless of whether any of them mentioned it.

Why finishing beats perfecting

The hardest skill in indie development isn't any particular technique — it's finishing. Most games that never ship didn't fail on talent; they failed on scope, polished forever, or chased one more feature. The developers who build a real body of work are almost always the ones who got good at choosing something small enough to complete and then completing it.

That's worth keeping in mind here, because it's easy to let any one part of development expand to fill all your time. Decide what 'good enough to ship' looks like, protect that line, and treat the endless list of possible improvements as a backlog rather than a set of obligations.

Plan for the parts you can't see

Once a game leaves your machine, a lot of what happens to it becomes invisible by default. Players run it on hardware you don't own, hit problems you never reproduced, and most of them never tell you — they simply move on. The gap between 'it works for me' and 'it works for everyone' is where a surprising amount of churn quietly lives.

So plan to see what you otherwise couldn't. Watching real players, capturing the bugs and crashes they hit with the context to fix them, and paying attention to where they drop off all turn invisible problems into ones you can actually act on — which protects the reviews and retention everything else depends on.

Small regular sessions beat rare marathons, and scope to the hours you actually have. The job removes the pressure.