|
|
|
|
|
|
by chrisandchris
1219 days ago
|
|
|
It's interesting how you differ between "deploy ASAP, within half a day" and "keep the fix a few months back". Like, is there nothing in between? Like once a week, once every other week? If you would have to estimate, wouldn't be there less bugs if you would deploy less fast (and use this time for validation)? |
|
|
I've worked on products across the spectrum, Enterprise software that releases twice a year, smaller stuff that ships once a month, and now a SaaS that releases many times a day. I don't have the data to compare, but I genuinely don't believe the rate of bugs was materially different between any of them.
We make faster changes, but the changes are much smaller, and so the surface area to test is smaller. The more changes you make, the more time you need to validate. If you make a weeks worth of changes, you're going to need an appropriately longer validation cycle than if you make 1 change. It scales, and in my experience, many products with slower release cycles aren't appropriately scaling up the validation time to match.
That said, this doesn't necessarily mean we're writing code and 30 minutes later its in production...there's still an iterative dev cycle with lots of validation happening...but if something is ready to go, ship it!