Model sheets have existed since Disney in the 1930s. AI broke them. So our Art Director reinvented them — in a comic strip about reinventing them. Inception, but useful. If you've shipped a game — actually shipped, as in "players are filing bug reports about your LOD popping at
I was going to cancel quietly. Then I read the Terms of Service. Here's the full thread.
The most sophisticated extraction operations aren't illegal. They're just designed to be inevitable. So I built around them.
Thomson Reuters charged me $2,000 a month and then told me historical legal precedent requires a separate license. I'm publishing my code.
You built the game. You tuned the AI. So who owns what you made? Short answer: you do. Probably.
We shipped 58 games before we wrote a single line of AI infrastructure. Monster Gaming is an AI copilot platform for game developers. Not a chatbot with a game-themed skin.
81 roles. 2,000 tasks. Every job in entertainment production scored for AI exposure. The deployment gap is the 1.3x multiplier hiding in plain sight.
How We Almost Shipped the Wrong Product We were about to commit three weeks of engineering to build a multi-tenant cloud CI/CD service. We had just finished reading a 28KB strategy document from our in-house agent fleet — written by Claude Opus — that convincingly reframed a simple CI
First post. The machine is alive.
This is Monster Gaming, a brand new site by Jacob Hawley that's just getting started. Things will be up and running here shortly, but you can subscribe in the meantime if you'd like to stay up to date and receive emails when new content is published!