Part of the "How to bring order to a project" series — the infrastructure track. Same starting point: a growing gamedev project, nearly two dozen services on different stacks — Python, Go, C++, a mobile client — and infrastructure that grew faster than it matured. Every service deployed differently, configs lived on servers, and a new service was born by copy-pasting the oldest one. Attacking this with a "big refactoring" is a road to nowhere: the business won't let you stop shipping featur...