Version Control When the Repository Is Mostly Binary Assets
Choosing version control for game repositories where binaries dominate, covering Git LFS, centralized asset systems, hybrid models, build farms, and remote studios.
Signed opinion on making games: production, live ops, players and the tools studios build with. Short positions from the people doing the work.
Where the articles follow an argument you can’t stop having, the blog takes a position on the work behind the game: how it is planned, shipped, run and built.
Choosing version control for game repositories where binaries dominate, covering Git LFS, centralized asset systems, hybrid models, build farms, and remote studios.
Subtitles, remappable controls and motion options aren't a niche feature; they open the game to more players in more situations. The cheapest time to build them is before your systems harden.
How to choose between spreading workloads across nodes and bin-packing them onto fewer nodes, based on the capacity contract, the autoscaler, and the workload's failure mode.
Engine source, unreleased assets, design documents, and platform SDKs covered by console NDAs cannot go to a hosted AI service. Open-weight models run on your own hardware keep the data in the building, but they differ in license terms, acceptable-use restrictions, coding ability, hardware requirements, and what is known about their training data.
Interactive world models are forcing engine teams to reconcile deterministic simulation with probabilistic generation, and the split between diffusion and JEPA architectures maps directly to how studios already separate rendering from physics.
Players won't remember that the servers recovered by dinner; they'll remember the queue that reset their progress. Test realistic arrival spikes across the whole player journey, and rehearse the response.
Randomised paid rewards can spike revenue while leaving players uncertain and regulators interested. Engagement built on visible progress, direct sales and social play lasts longer.
Reviews, forums, support tickets and telemetry point at the same pain points, but feedback sits because turning it into action feels overwhelming. Close the loop, internally and in public.
Crunch is what happens when the plan stops telling the truth: the milestone slips, the scope stays, and overtime quietly becomes the schedule. Cut early and protect the time for polish.
Big updates pack in risk: shifting release candidates, repeated retesting and blunt rollbacks. Smaller, predictable releases are a risk-management strategy, as long as each one has a plan.
Making games while the tools keep changing? Get our research brief on AI, game design and production. See what generated assets and faster answers mean for the work—and bring better questions to your next design discussion.
Occasional dispatches, when there is something worth your attention.