ENGINEERING / TOOLS & TRUST
The smallest studio in the room has a surprisingly big toolbox.
AI-assisted engineering changes what one person can attempt. It does not remove the obligation to know whether the thing actually works.
I have spent much of my professional life explaining what computers are capable of doing for people. Lately the question has changed: what can a person build when the computer can help with the building itself?
For a small creative studio, the answer is: quite a lot. Code, documentation, test harnesses, content pipelines, art workflows and production builds can all move together. That does not mean you get to skip thinking.
Work packages beat wishful prompts
Good collaboration is concrete. Here is the desired behavior. Here is the repository. Here are the boundaries. Here is what is allowed to change, what must stay untouched, and how we will prove the result. “Make it better” is a mood, not a specification.
My preferred division of labor is to define the experience and acceptance criteria, then let the implementation explore reasonable solutions inside those constraints. I review the result in the actual program, not merely in a convincing completion report.
A passing test is evidence, not a halo
Automated checks are essential. They also have scope. A successful saved-game continuation proves something different from a human finishing a fresh campaign without assistance. A test rig reaching an ending is not proof the path is fun. A build with zero errors can still have an aquarium full of bad art.
Useful reports make those boundaries obvious: what ran, what failed, what remained staged, what changed in production, and how to roll back. I want the evidence and the uncertainty in the same paragraph.
Quality is still an authored decision
There is a point where the work becomes taste: the curve of a camera, an interaction that feels awkward, the rhythm of a scene, whether the art can breathe. That is where I want to spend more time, not less.
For me, automation buys the right to be picky. It makes iteration cheaper so I can concentrate on the details that do not fit in a pass/fail test. Sometimes that means spending an afternoon on a shoreline nobody will notice consciously—and everybody will feel.
The caution is not optional
Keep source control, backups, explicit scopes and meaningful review gates. Do not put confidential material into a public artifact. Do not confuse a tool that produces fluent language with a tool that has verified the world. Keep a place for dissent, test failures and human decisions.
That is not anti-automation. That is how a tiny team can afford to be ambitious without outsourcing responsibility.
The machine shop is faster. The person deciding what is worth making still matters.
Personal commentary and work-in-progress thinking. Historical workplace material is used only as private research context; this page does not disclose private operational records. Descriptions of planned features are not claims of released software.