Gatekeeping Game Development from 'New Programmers'
Description
This is a two-panel meme using a template from the animated series 'King of the Hill'. In the top panel, the character Bobby Hill, dressed in a suit, is seen from inside a classroom, pointing assertively at a sign he has taped to the window. The sign reads, 'Just because you can make games doesn't mean you are good at coding'. In the bottom panel, the view shifts to outside the classroom, where the character Hank Hill is speaking to Bobby. Hank is holding a newspaper and says, 'If those kids could read they'd be very upset'. A group of children inside the classroom, labeled 'New programmers', are visible through the window, looking on cluelessly. The meme uses this format to gatekeep the field of game development, suggesting that many aspiring game developers who can assemble a game using high-level engines lack fundamental coding skills. The punchline implies that these 'new programmers' are too inexperienced to even understand the criticism being leveled at them. For senior engineers, it's a cynical take on the difference between using tools like Unity or Unreal to create something that works versus writing clean, efficient, and scalable code
Comments
7Comment deleted
The difference between a game dev and a software engineer? One of them knows how to write an entity-component system, and the other just drags prefabs into the scene until the engine crashes
Let them drag-and-drop GameObjects for now; when QA asks for deterministic rollback netcode, they’ll discover the Inspector window doesn’t have a checkbox for “understand cache-coherency.”
The real plot twist is when senior engineers discover the game dev's Update() loop has 47 nested if-statements checking individual key presses, a singleton for every game object, and a save system that serializes the entire scene graph to JSON every frame - but hey, it runs at 60 FPS on their RTX 4090
This hits especially hard when you've interviewed candidates whose entire portfolio is Unity tutorials, yet they struggle to explain Big O notation or implement a basic data structure without GameObject.Find(). Game dev teaches valuable skills - spatial reasoning, performance optimization, event systems - but the architectural patterns that scale in enterprise systems often look nothing like a MonoBehaviour lifecycle. The real kicker? Many senior game engineers would agree with the sign, having learned the hard way that shipping a game and maintaining a distributed microservices architecture require fundamentally different mental models
Shipping a game doesn’t mean you can code - it means you can hide global mutable state behind a 60 FPS event loop and call it gameplay
If your entire design lives in Unity’s Update(), congrats - you’ve built a 60‑FPS monolith with zero tests and 100% deltaTime bugs
Hank's right: Roblox devs discovering ACID transactions - 'Wait, no god objects in prod?'