This resonates from a non-technical perspective too. As someone in marketing at a tech company, I've seen firsthand what happens when infrastructure is deferred it doesn't just create technical debt; it creates communication debt. When infra isn't standardized early, every deployment becomes a fire drill. And fire drills kill content calendars, launch timelines, and product announcements. Marketing ends up either waiting on engineering or pushing releases before they're stable. The shift you're describing, where Dockerfiles and Kubernetes configs ship as default build outputs, actually makes cross-functional work cleaner. When infra is predictable, everything downstream becomes predictable too. Infrastructure isn't just an engineering problem. It's a business rhythm problem.