I'm of the mindset, and ever more so... reducing the number of environments from source to production and trunk-based development is a better way to go. "Don't

I'm of the mindset, and ever more so... reducing the number of environments from source to production and trunk-based development is a better way to go. "Don't break production!" In the end, getting rid of longer testing cycles, and faster paths to production allows one to change fast and reduce the risk that is inherent to longer release cycles. Especially when you only have a single production deployment for a website/service. Having one gate between is probably okay (test/demo), but more means there's more chance of breaking things when trying to merge and reason with ever broadening code bases. Especially with smaller teams. Yes, this all means production may break, but it also means the lesson is learned, devs get more careful, and testing evolves more rapidly out of necessity or pain.