Production incidents from not carefully scrutinizing changes is a sign that someone more senior should be putting infrastructure in place to minimize the impact of those incidents.

Feature flags, staggered rollouts, quick rollbacks, smoke testing, etc.

Sure, if you were hand managing every rollout up until now, and relied primarily on unit tests, you’re in for a world of hurt when you give a junior engineer Claude code and let em rip.

But if you have more advanced systems to measure and maintain overall service health, and codify your business logic invariants, you can really start flying these days as long as you’re all aligned on what to build and the potential impact.