3 ms·
Half an hour is 30 times longer than I want to wait for good quality feedback. I’ll settle for under 5 minutes, but I always shoot for 1 minute. 30 minutes is
by glenjamin 5y ago
Half an hour is 30 times longer than I want to wait for good quality feedback.
I’ll settle for under 5 minutes, but I always shoot for 1 minute.
30 minutes is not really compatible with continuous deployment approaches
- lmm 5y agoIMO a deployment that doesn't contain a user-facing feature is meaningless - so rather than being able to deploy literally every second, you only need to be able to deploy fast enough to make each user-facing feature (which is probably, what, 1/week/developer?) its own deployment. So assuming you have the kind of team size that I think is right (which is a whole other discussion), half an hour is good enough. (I'd still call that continuous deployment, because master is continuously deployed - but you only have feature branches landing in master at a rate of one per 30 minutes). Your test-edit cycle should definitely be much shorter than half an hour, but you don't need to run the full test suite for that.