Jason Respress

I build games and the AI tooling behind them at OTG Studio, and write about what agents can and can't be trusted to do.

Writing

  1. Cohorts: What Changes When More Than One Team Is Working With Agents

    When more than one team works with agents, the seam between them is a ledger of measured claims that the receiving side re-verifies, not shared context.

  2. AI Agents Don't Need Better Prompts. They Need Better Managers.

    Nine months running a development organization of one human and a rotating workforce of AI agents. What made it work was not prompt engineering. It was management.

  3. A Year of Betting on Local AI for Game Dev: What Worked, What Didn't, and What's Actually Blocking It

    What a year of building game-dev tools on local AI models taught me: the system matters more than the model, integration is mostly plumbing, and a few hard limits still keep local AI out of shipped games.

All writing

From the dev log

  1. Day 1, part 2 of 3: The cast arrives

    Eight characters went from generated models to rigged Unreal actors whose clothes move. Their faces didn't pass review, so they're paused. The sets went back to the drawing board, and the score arrived in stems.

  2. Day 1, part 1 of 3: The first playable

    PRINT IT! is a fight picture you direct and star in. By Thursday morning a placeholder cast fights fairly, calls Cut!, prints takes, and the game cuts them together with a camera that swings around the action.

  3. Day 0: The theme, the rules, and an empty project

    The theme is Director's Cut. The rules say gameplay and art get made during the four days, so the engine I'd built stays out and the game starts from an empty Unreal project.

Projects

In production

PRINT IT!

Direct and star in a cheap 1970s fight picture. Call Cut!, print the take you love, and watch the game cut it into your Director's Cut.