Game Developer ≠ Programmer (And Why It Matters)

Being a game developer doesn't mean being a programmer. Coding is one tool inside game development — a very powerful one — but the real job is deciding what to build, how it should work, and whether it's actually fun. In this video I talk about why "what engine?" misses the point, why technically excellent systems can still make a worse game, what Undertale, Celeste, To the Moon and Stardew Valley tell us about code vs. decisions, and why the question is shifting from "can you make a game?" to "can you make a game worth playing?" So — are you a programmer, a designer, an artist… or a slightly bad version of all three? Tell me in the comments. ⏱ Chapters 0:00 "What engine?" 0:41 The wall called code 1:11 Who actually makes a game 1:40 The tools changed everything 2:12 Two people: programmer vs game developer 3:02 Building systems vs building the game 3:27 Technically excellent, still a worse game 3:50 Can I build this? Should I? 4:15 Proof: Undertale and Celeste 4:55 Coding still matters 5:21 Stardew Valley and good decisions 5:43 Asset flips prove the point 6:33 Players don't care how hard it was 6:55 The flip side 7:31 Taste, scope, design 7:55 "Game developer" is a broad term 8:39 The hardest part of making games 🎮 Games shown To the Moon — Freebird Games Undertale — Toby Fox Celeste — Maddy Makes Games Stardew Valley — ConcernedApe (Eric Barone) Gameplay footage is used for commentary and criticism. All rights belong to their respective owners. #gamedev #indiedev #gamedesign