> That’s essentially why we don't have a staging environment and why “dev” is a direct copy of prod but with different backing data. That's fair, and a decent

> That’s essentially why we don't have a staging environment and why “dev” is a direct copy of prod but with different backing data. That's fair, and a decent way to make a staging environment, though as echoed elsewhere, the data itself can exercise your code in ways that uncover bugs. I think also this is more feasible on, say, a monolith setup, vs a sharded multi-cluster service that's integrated with manifold 3rd party systems - but yes, if you can, you probably should have this kind of prod-replica staging in adjunct to incremental canary rollouts, prod-safe testing suites etc. and also the article was explicitly suggesting in-prod testing should be adjunct to non-prod testing