Comment by jimbo_joe

The blog post nails the problem well: with distributed training handled by many teams the problem becomes organizational rather then tech-based. Having a technology solution to more easily persist pipeline and artifact configs is a good idea, but it only yields an incremental improvement. IMO this can only solved with a shared culture around experimentation which has to be maintained and reinvented as the company (and hence the teams responsible for training) grows. Basically, if every layer of the stack from tooling to training to applied are aiming for repeatable training with predictable capability improvements that end users can see, then it's more likely to happen.