You Don’t Need to Code to Be a Game Developer

By RookieDev

Community Score: 50% | 255 views | 1w

0 community ratings: null thumbs up, null thumbs down

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 mat

Tags: game development, game developer, game design, indie game development, indie dev, solo game dev, visual scripting, RPG Maker, Undertale code, Stardew Valley, To the Moon, game engine, learn game development, making games, game dev, indie game, game programmer, programming, coding, indie developer

More from RookieDev

  • Core Game Mechanics Explained – From Idea to Gameplay (Game Mechanic Design Tutorial Part 2) — Score: 50%
  • Build Better Platformer Controls Today — Score: 50%
  • Practical Game Design Series (Let's Build) — Score: 50%
  • Build Fast or Fall Behind in Game Dev — Score: 50%
  • Hades 2 Proves Small Teams Beat AAA Studios — Score: 50%
  • Why Some Games Just Click – The Hidden Design Trick (MDA Explained) — Score: 50%