> Deploy everything all the time More often than not, this ends up being a business decision about balancing risk with potential loss of revenue (you don't wan

> Deploy everything all the time More often than not, this ends up being a business decision about balancing risk with potential loss of revenue (you don't want to take your stuff down, but you also don't want to delay new features that could bring more business) Fast growing companies trying to enter the market tend to favor "deploy more often, break more often" while companies with large, established bases tend to favor "more testing, more deliberate changes" I would say the inverse is a better rule "you should be /able/ to deploy any time"