> There is absolutely no way they have control over what gets produced at that rate.

I'd wage that volume of changes is not leading to forward progress, but is a clear sign of code churn.

This in turn is a clear tell they are dealing with spaghetti code.