Game Design / Development

A game starts as nothing. There is no world, no character, no rule, no consequence — and then someone decides that pressing a button makes a thing jump, that falling into the pit ends the run, that collecting the coins unlocks the door. Out of pure decisions, a working little universe appears with its own physics and its own logic, and a stranger you will never meet picks it up and plays inside the rules you invented. That is the structural pull of the field, and it is Creation in its most literal form. Almost everything else in game development sits underneath that one fact: this is a field for people who want to bring whole experiences into existence that did not exist before, and watch other people live inside them.

What surprises most people who enter is how much of the daily reality is the opposite of that romantic image. Creation is the pull, but the daily texture is dominated by Resolution and by iteration. A game is the most stubbornly interactive thing you can build — every system touches every other system, and a small change to how the player moves can quietly break the enemy AI, the camera, and the save file all at once. The running truth of the field is that you do not design a game and then build it; you build a rough version, play it, discover it is not fun, and change it, hundreds of times, until it is. "Fun" is not something you can specify on paper — it has to be found by making the thing and feeling it, which is why the prototype-playtest-revise loop is the real engine of the work and why so many hours go into making broken things functional and unfun things fun.