2 ms·
I've found in practice the effort to go from a -> b -> c -> d in aggregate is often far less than the effort to go from a -> d. In addition I've found the stab
by noir_lord 11y ago
I've found in practice the effort to go from a -> b -> c -> d in aggregate is often far less than the effort to go from a -> d.
In addition I've found the stability of the system as a whole is better when you swallow the pie in small chunks and when your project depends on multiple dependencies upgrading them gradually piece at a time makes bisections much simpler than "stop the world and update".
It really does depend (as most things do) on the particular domain/problem/solution though, if I was working on something that ran for years and couldn't be touched in production I'd probably go the other way.