/ Game Dev With AI / How to Get Into Game Development Without a Degree
Game Dev With AI • • 11 min read

How to Get Into Game Development Without a Degree

Get into game development without a degree using a $0 tool stack with licenses checked, a 12-week plan, a four-rung portfolio ladder and the failures to expect.

How to Get Into Game Development Without a Degree

How to get into game development without a degree comes down to one substitution. A degree is a document that says you can finish things. A portfolio of small, published games is the same document, and it costs $0 in software. Install Godot, build the official tutorial game in a weekend, put it on itch.io, then climb four rungs of increasingly bigger finished games over about 12 weeks. That is the plan. The rest of this article is the tool stack with each license read today, the ladder, and the ways it goes wrong.

I should say where I sit. I ship small games in Godot, I have a folder of six shelved projects next to the one I finished first, my channel has seven subscribers, and the roughly $10,000 I've made across everything I've shipped is not a game number worth bragging about. That is the receipt this article runs on. It is small, and it is real, and it is more than most of the pages that rank for this phrase will show you.

What "Without a Degree" Actually Replaces

The career guides that rank here tell you a bachelor's in computer science is what studios look for and then cite a salary. The two I read cite different numbers from different sources, one of them with no source at all, so I'm not repeating any of them. The government page that would settle it returned an error to me today. Take the salary talk as noise.

What a degree signals to a hiring manager is that you completed a multi-year thing with deadlines. What it signals to you is that you know the basics. Both signals can be replaced. The first by finished games anyone can download. The second by the engine's own documentation, which is better than most courses and free.

Neither replacement works if the games are unfinished, and this is the part the career guides skip because it is unflattering, so I'll be plain about it from my own folder, where six projects with more ambition than the one that shipped are still sitting, unfinished, exactly where I left them. A folder of prototypes is not a portfolio.

The $0 Stack, Licenses Read Today

Every tool below is free of charge and every license was read on September 15, 2026 from the project's own page. The license matters because "free" sometimes means "free until you sell something," and none of these do that.

Tool Job License What you own
Godot 4.7.2 engine and editor MIT the license page says you "will be their sole copyright owner(s)" of what you make; include the engine's license text in your credits
Krita 2D art GPL v3 "What you create with Krita is your sole property," per the Krita license page
Blender 3D models and animation GPL usable "by game artists to work on commercial games," per the Blender license page; no registration, no internet needed
Audacity sound editing GPL v3 your recordings
itch.io publishing free account, 10% default share on sales you can set to 0% your game and your page

Total cash outlay is $0.

The only fee anywhere in this stack is itch.io's flat $3.00 tax identity fee, per its payments page, and only if you switch on payments. A free or donation-optional page never triggers it.

You will read advice to learn Unity or Unreal because studios use them. Maybe later. For getting in without a degree, the engine that costs nothing and makes you the sole owner of your output removes every reason to stall. Switching engines after two finished games is a two-week problem. Never finishing is a two-year problem.

The 12-Week Plan

Twelve weeks is my number, not a study. It is long enough to climb four rungs and short enough that a job or a family does not eat it. Each rung ends with something published where a stranger can play it.

Weeks Rung Build Ship it to What it proves
1 Tutorial game Godot's official Dodge the Creeps, all seven steps itch.io, free you can follow docs and run a full pipeline once
2 Jam game a 48 to 72 hour jam entry, any jam on itch.io the jam page you can finish under a deadline and cut scope
3 to 6 One-month game one mechanic, three levels, a title screen, sound itch.io, free or donate you can design and sustain a project past the novelty
7 to 12 Three-month game your own idea at the smallest scope that is still a game itch.io, and a Steam page if it deserves one you can carry a project through the boring middle

Four published games in three months. Not one polished game. Four. The number of finished things is what replaces the degree, and it is also what teaches you, because the last 10% of a game is the only part that teaches you the last 10%.

Rung One, the Tutorial Game

Godot's first 2D game tutorial builds Dodge the Creeps, a game where "your character must move and avoid the enemies for as long as possible." Seven steps, an asset pack provided, and a completed project on GitHub if you get stuck. The docs say it is meant for people who did the step-by-step introduction first, and I'd take that seriously. The intro is a few hours and it is where the words scene, node and signal stop being mysterious.

Do not customise it. Do not swap the art. Build it exactly as written, export it for the web, and put it on itch.io using the publishing preflight on this site. The point of rung one is that your pipeline works end to end, from an empty project to a URL. The first Godot game guide here covers the traps that stop people during that weekend.

If this rung takes two weekends instead of one, fine. If it takes six, something other than skill is in the way, usually customising too early.

Rung Two, the Jam Game

itch.io describes itself as "a place for hosting and participating in game jams online," and its jams page says anyone can create and host one. The counter on that page read 598,954 jam games when I loaded it today. There is always a jam running.

Pick a short one, 48 to 72 hours, and enter with the goal of submitting, not placing. A jam does to scope what nothing else does. You will cut the second enemy, the menu, the story, and the game will still exist at the deadline. That experience is the single skill a degree does not teach and every studio wants.

Reuse the movement and the export settings from rung one. Nobody cares that your jam game is a reskin of Dodge the Creeps with a twist. They care that it is on the jam page.

Rung Three, the One-Month Game

Now design something. One mechanic, three levels that each change the mechanic's situation, a title screen, a restart, one sound effect and one music loop. Write the scope down before you open the editor, using the scoping method on this site, and treat the written scope as a contract with yourself.

The month is where the shelved projects come from. Mine died here, all six, and the pattern was the same each time. Week one is fast, week two adds a feature the scope did not have, week three discovers that feature broke the plan, and week four is spent avoiding the project. The fix is not more discipline. The fix is a scope small enough that week two has nothing to add.

Ship it free or donation-optional. itch.io's pricing page explains that any price you set is the minimum and downloaders can pay above it, so a $0 page still lets someone tip you. I would not price rung three. Its job is to exist.

Rung Four, the Three-Month Game

Your own idea, at the smallest scope that still deserves the word game. Six weeks of building, two of polish, and the rest for the store page, a trailer, and the boring parts you skipped on the earlier rungs, like settings and a proper pause menu.

This is the rung that goes on a portfolio page or a job application, and it is the one where the earlier rungs pay off, because by now the pipeline is muscle memory, the scope discipline is real since a jam already forced it once, the failure patterns are familiar since you already hit every one of them in month one, and the store page and trailer are no longer mysterious chores but the last two items on a list you have run three times. When people say "make lots of small games," which the forums that rank here say in every thread, this ladder is the operational version of that sentence, with the sizes and the deadlines filled in so that the advice can actually be followed by someone who has never finished anything.

After rung four the question changes from "how do I get in" to "how do I release," and that is a different article.

Where This Plan Breaks

Every plan on the internet is written by someone who finished. Here is where I'd expect this one to fail, from the folder of ones that did.

Failure What it looks like Week it usually hits What to do
Customising the tutorial new art before the game runs end to end 1 build it stock, ship it, then reskin as a separate project
Skipping the jam "I'll do a jam after my real game" 2 the jam is the real game's training; enter one this week
Scope creep at week two a feature the written scope did not include 4 or 5 cut it or write it into the next rung's scope
Engine shopping reading Unity vs Godot threads instead of building any switching is a two-week cost after two shipped games, never before
Devlog to nobody seven subscribers, no comments, the urge to stop posting 6 onward post anyway; the log is for the portfolio, not the algorithm
Polishing rung three month two on a game whose job was to exist 7 ship it as is and start rung four
Waiting for the idea rung four never starts because the idea is not good enough 7 take the mechanic from rung three and add one constraint

That devlog row is mine. Seven subscribers on the channel, and a site that averages position 47 in search. Both are still running. The portfolio does not care how many people watched you build it. Whoever evaluates you opens the game, not the channel.

Too Old, Too Late, Replaced by AI

Three of the questions people ask around this phrase are versions of "is it pointless." Short answers.

Twenty-three is not too late and neither is twenty-five, and I say that as judgment, not statistics, because I have no data on age and hiring and I'd distrust any page that claims to. The ladder above takes 12 weeks. The age at which 12 weeks stops being available to you is not one I know.

Will AI replace game developers is a longer question and this site has a whole article on where AI actually helps. The short version is that it writes boilerplate and explains errors well, and it does not finish games or decide what is fun. The skill the ladder builds is finishing. That is the one I'd bet on.

The Only Metric That Counts

At the end of 12 weeks you should have four URLs. Not four projects, four URLs, each one a game a stranger can play. If you have three, you are ahead of most people who searched this phrase. If you have one, you learned the pipeline, which is more than a semester of theory gives you.

A degree takes years and costs money. This takes a quarter and costs $3 if you decide to turn on payments. The trade is that nobody hands you the paper at the end. You have to click publish four times yourself.