Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Gameplay programming
Build a small playable game with movement, collision and scoring
What you'll learn
Game loop
Fixed timestep
State machines
Profiler evidence
Practice
Review an NPC State Machine for Logic Gaps20 min
Design a Frame-Rate Fix for a Physics-Dependent Game25 min
Chapter 2
Programming languages
Build small programs in one language, handling input and errors
What you'll learn
Types and values
Control flow
Error handling
Asynchronous work
Chapter 4
Code quality
Review code for unclear names, then tidy a messy function
What you'll learn
Clear names
Single responsibility
Review the risk
Explain the reason
Proportionate change
Practice
Review Code for Quality Issues15 min
Chapter 4
Reading code
Explain unfamiliar code and predict what a function outputs
What you'll learn
Feature entry point
Call chain
Reference search
Code reading notes
Practice
Read 100 lines of unfamiliar code30 min
Chapter 4
Debugging
Use error messages to find bugs and explain your fixes
What you'll learn
Hypothesis before keyboard
Reliable reproduction
Root cause, not symptom
Narrow it down
Reading a stack trace
Practice
Find the Bug Using an Error Message10 min
Triage Five Bug Reports by Severity10 min
Chapter 6
Git
Save clear changes to a project's history and request review
What you'll learn
Change states
Short-lived branches
Merge conflict
Useful commit message
Pull request review
Practice
Rewrite 5 bad git commit messages15 min
4 more in the plan
Adapting to changeTry a new tool and describe how you handled changeCh 7
What you'll learn
Change vs your response
The messy in-between
Not there yet
Real change vs a feeling
Practice
Map a Change You've Already Survived15 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 8
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 8
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Problem solvingTest each possible cause of a problem instead of guessingCh 8
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Your plan
Chapter by chapter.
12 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of a Game Developer
StartFree
2~2 wks
Program gameplay that feels right to play
Skills
3~2 wks
Explain a system you built in writing
Project
4~2 wks
Read, review and fix code others wrote
Skills
51–2 wks
Talk to two working game developers
People
6~2 wks
Track every change to your code
Skills
7~2 wks
Adapt well when work changes
Skills
8~2 wks
Explain problems and solve them together
Skills
9~2 wks
Capstone: build and release a small game
Project
101–2 wks
Answer the questions interviewers ask
Interview
111–2 wks
Decide how you will get in
Decide
12on your timeline
Send your first applications
Apply
The job
What a Game Developer does
Writes the code that makes a game run: how characters move, how the physics feels, how enemies behave, and how everything draws on screen. This is a programming role inside a game engine such as Unity, Unreal Engine, or Godot, and it is different from a game designer, who shapes the rules and feel rather than writing the code.
The work
Write gameplay code for movement, combat, scoring, and game rules
Build physics and hit-detection (collision) so objects move and bump believably
Program enemy and non-player character (NPC) behavior using game AI
Wire up visual effects and use the engine's graphics and lighting tools for scenes
Optimize frame rate, memory, and load times for target devices
Fix crashes and bugs found in testing and player reports
Wire up controls, menus, and save systems across computer, console, and mobile
A typical day
Check the bug tracker and team chat for blockers and crashes
Plan tasks in a short stand-up, then start a focused coding block
Build a gameplay feature, then test it live in the engine
Profile performance, find a slow frame, and optimize the code
Review a teammate's code, then fix a reported crash bug
Commit changes, update notes, and sync the build for testers
Tools
Game engines: Unity, Unreal Engine, GodotProgramming languages: C#, C++, GDScriptVersion control: Git, Perforce3D and art tools: Blender, MayaProfilers and debuggers: Unity Profiler, RenderDocIssue tracking: Jira, TrelloBuild and delivery: GitHub Actions, Jenkins
Ways in
There is more than one route.
Ways to study
Bachelor degree in computer science, software engineering, or game development
Diploma or certificate in game programming with strong project work
Coding bootcamp or short course focused on Unity or Unreal Engine
Self-taught path using engine tutorials plus a portfolio of finished games
How people get their first job
Build and publish 2 to 4 small games on itch.io with clean code
Join game jams to ship a playable game in a weekend
Apply for junior gameplay programmer or engine internships at studios
Make free assets or tools for Unity or Unreal and share them
Start as a general software engineer and move into a game team
How long does it take to become a game developer with Welica?
The plan is 12 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelor degree in computer science, software engineering, or game development, diploma or certificate in game programming with strong project work, coding bootcamp or short course focused on Unity or Unreal Engine, or self-taught path using engine tutorials plus a portfolio of finished games.
What is free?
Chapter 1, See the work of a Game Developer, is free for good. Premium unlocks the rest of the plan.