Programming and Software Development
Game development
Game development combines real-time programming, graphics, physics, audio and design into software that has to respond within a fraction of a second, frame after frame. Most work now happens inside engines such as Unity, Unreal and Godot, which supply rendering and physics so teams can concentrate on the gameplay loop. The field has its own tools and release pressures, and a job market that values finished, playable projects over credentials.
Why this topic exists: Engines, graphics, physics and the design loop are a development field with its own tooling and job market (Udemy's Game Development shelf; SFIA Animation development).
A game is a program that runs a loop: read the player's input, update the world, draw the result, and do it again, many times a second. At sixty frames per second each pass has roughly sixteen milliseconds for physics, animation, AI, audio and rendering together, and missing that budget is visible to every player as stutter. That constraint shapes game code more than any other. It is why the field cares about memory allocation, data layout and profiling in ways most business software never has to.
SFIA places this work under animation development, a skill that covers games alongside simulations and virtual environments, and the overlap is real: the same engines drive training simulators and architectural walkthroughs. Within a studio, roles divide into gameplay programmers who build mechanics, engine and tools programmers who build the machinery, technical artists who connect art to code, and designers who decide what should be fun.
Three engines, three trade-offs
| Engine | Scripting | Typical ground | Worth knowing |
|---|---|---|---|
| Unity | C# | Mobile, independent and 2D or 3D games, plus AR and VR | Proprietary licence; read the current terms before committing a project |
| Unreal Engine | C++ and Blueprints visual scripting | High-fidelity 3D on PC and console, film and visualisation | A heavy toolchain that expects capable hardware |
| Godot | GDScript or C# | 2D and smaller 3D projects | Open source under the MIT licence |
Around the engine sits an asset pipeline. Models and animations are made in tools such as Blender, textures and audio elsewhere, and all of it has to be imported, compressed and versioned. Python appears here more than in the games themselves, scripting Blender and automating build and asset tools. Because large binary files and long import times grow with every level added, studios tend to invest in pipeline tooling early rather than after the project has become hard to build.
Where first projects go wrong
- Scope that could keep a studio busy for years. A small game that is finished teaches more than a large one abandoned.
- Following tutorials end to end without ever changing the design, so nothing learned is truly your own.
- Allocating new objects every frame and wondering why the game hitches.
- No version control, or plain Git struggling with large binary assets it was not designed for.
- Skipping playtests. What feels obvious to the person who built a level rarely does to a newcomer.
Hiring in games rests on evidence you can play. A short, polished game with clear controls, a menu and an ending says more than a certificate, and game jams are a good way to produce several within tight limits. Related ground lies in programming languages for choosing between C# and C++, 3D and animation on the art side, mobile development for phone releases, and software engineering practice for keeping a growing codebase in order.
Next to this topic
- Programming fundamentalsOne language learned properly plus enough of the machine beneath it: variables, control flow, data structures, debugging and reading code (SFIA Programming/software development; MDN's getting-started modules).
- Programming languagesPython, JavaScript, Java, C#, C and C++, Go, TypeScript, Rust, Kotlin, Swift: what each is for and where it is hired, so the first choice is a career decision rather than a syntax preference (Udemy's Programming Languages shelf names the market).
- Web developmentHTML, CSS and JavaScript, then a framework and the browser's APIs: MDN's core and extension modules are the syllabus of the largest development field.
- Back-end development and APIsServers, frameworks, databases behind them and the HTTP and REST contracts between services (MDN server-side modules; DVA-C02; the freeCodeCamp back-end certificate).
- Mobile developmentiOS, Android and the cross-platform frameworks are their own toolchains, stores and review rules (SFIA Systems development; Udemy's Mobile shelf).
- Databases and SQLThe relational model, SQL, schema design and the document and key-value stores next to it: the layer every application and every analyst stands on (SFIA Database design; DP-900 relational concepts).
- Software engineering practiceVersion control, code review, testing habits, architecture, design patterns and clean code: the slow layer hiring quietly filters on (SFIA Systems and software lifecycle engineering; MDN version-control module).
- Software testing and QATesting as a discipline: the ISTQB Foundation syllabus v4.0.1 (fundamentals, testing through the lifecycle, static testing, analysis and design, managing test activities, tools) plus the automation frameworks (Selenium, Cypress, Playwright).
- DevOps, Git and CI/CDVersion control workflows, pipelines, containers for developers and the culture that joins build and run (AZ-400; GitHub Foundations and Actions; the cloud field owns infrastructure as code and operations).
- No-code and low-code developmentBuilding software without writing most of it (Bubble, Webflow, Zapier, Make, Airtable) is a recognised route into shipping products; Microsoft's Power Platform is the office-suite version of the same idea.
- AI-assisted developmentAssistants changed how fast plausible code appears, not what makes it correct; reading, testing and correcting generated code is now part of the craft (GitHub certifies Copilot use and, on its 2026 credentials page, agentic AI development).
Concepts to know
Glossary entries with the reason each one matters here.
- Python
A scripting language in several engines and a first language for many game programmers.
Tools of the trade
Frequently asked
- Which engine should I start with?
- Godot or Unity for a first 2D project, since both let you get something playable quickly; Unreal if you are drawn to high-end 3D and ready for C++ and a heavier toolchain. The concepts of scenes, components and the update loop carry across all three.
- Do I need C++ to work in games?
- Not to start. Many studios build gameplay in C# or in visual scripting. Engine programming and performance-critical roles do expect C++, so learn it if engine work is your goal.
- Do studios care about certificates?
- Rarely. Studios look at what you have built and shipped. A portfolio of small finished games, with the code available to read, is the credential that counts in this field.
Courses in the directory
757 courses are filed here; the top 6 by our ranking, details and the provider link on each course page.
Last reviewed 26 September 2026 · Getting Digital