4 ms·
Why do all changes have to end up in production immediately?
by shiranaihito 18y ago
Why do all changes have to end up in production immediately?
- teej 18y agoBecause having thousands of real users running your code gives you insight that automate tests simply cannot match.
- shiranaihito 18y agoYes, but they might give you a hard time too if you put out something silly before thinking things through.
- BeefingJection 18y agoThe obvious solution, of course, is to think things through.
- shiranaihito 18y agoRight, but doing that 50 times per day is more challenging than once, for example.
- jmathes 18y agoWhether you commit your code once in one batch at the end of the day or 50 times in 50 smaller chunks, you have the same amount of complexity about which to be careful. In fact it's more complex in the former case, because in the latter, for each push, you know that all the previous pushes are working.
- kragen 18y agoWhen something breaks in production, it's easier to figure out what it was and fix it if you only changed a few things since the last time you updated production.