Get in touch
For tool questions, project collaboration, or general inquiries, you can contact me directly here without leaving the portal.
The difference isn't the budget or the engine. It is a trait that is becoming increasingly rare in large studios: Deep Genre Literacy.
There is a widening chasm in the gaming industry. On one side, AAA companies churn out corporate slop. These are games that are technically proficient but emotionally hollow. On the other side, indie breakout hits feel vital and addictive.
The difference isn't the budget or the engine. It is a trait that is becoming increasingly rare in large studios: Deep Genre Literacy.
The slop we see today is a byproduct of a 9 to 5 corporate culture. In a massive studio, many developers treat game design like a software ticket for a banking app. They clock in, follow a Standard Industry Practice manual, and clock out.
When your research is limited to a PowerPoint of last year’s Top 10 Steam games, you aren't innovating. You are just replicating. You don't have the time or the obsession to find the magic that makes a game work at a microscopic level because, for you, it is just a job.
In music, the greatest producers are Crate Diggers. They don’t just listen to the radio. They spend decades in dusty basements finding obscure, crap records for a single, perfect sound.
This is what successful game developers do. They don't copy the hit. They find a sample of a mechanic in a 20 year old Japanese emulator title that everyone else has forgotten, and they build a world around it.
To be clear, I am not saying successful devs are simply people who play a lot of games. Spending ten hours a day on Call of Duty doesn't make you a better designer. It makes you a consumer.
The developers who win are the ones who go out of their way to engage with the history of the medium. They play a ton of niche, obscure games specifically to learn. They have the ability to instantly recognize a hidden gem mechanic in the middle of a broken, forgotten title. They are looking for the DNA of fun, not just a way to kill time.
As industry analyst Chris Zukowski recently noted, the most successful developers are the ones who play everything. They aren't just fans of a single hit. They have a microscopic eye for detail that allows them to see why a game feels good.
Zukowski describes a recurring conversation he has with developers that perfectly illustrates the gap between a creator who is reading the medium and one who is just skimming the surface:
"I will talk to a developer who says they love Hades 2, so they decided to make a game just like it. I will ask them: 'Have you tried other roguelites? Games like Rogue or Nethack?'
And they will say: 'No, I have only played my favorite game, Hades 2, and I played Hades 1. I am basically making Hades 3.'
Contrast that with the truly successful devs. They will tell me: 'There is this obscure game that only ever released in Japan. I had to track down an emulator just to play it. The rest of the game is actually crap, but it has this one specific, incredible mechanic, and I put a version of it in my game.'"
The most successful authors in history are almost always the most voracious readers.
In game development, playing is reading. If you aren't playing obscure, difficult, and even crap games to see how they do it, you are literarily illiterate in your own field. You are trying to tell a story without knowing the alphabet.
AAA companies produce slop because they hire workers to execute a plan. Successful indies thrive because they are led by Crate Diggers and Voracious Readers who have a microscopic eye for what feels good.
If you are a game developer who doesn't play games, you should rethink what you are doing. You aren't creating a new world. You are just talking to yourself in a language you haven't bothered to learn.