3 ms·
> If you're building decoupled code you shouldn't need cross project changes. That's the theory, but in practice designing robust, future proof APIs has prove
by remus 9y ago
> If you're building decoupled code you shouldn't need cross project changes.
That's the theory, but in practice designing robust, future proof APIs has proven to be really hard in a lot of cases. You're then left with the option of supporting old APIs forever or migrating dependent code to new APIs, both of which are difficult in their own ways.
- jayd16 9y agoThat has nothing to do with requiring an atomic cross project change. If your depended library needs to be updated, update as needed. Upgrading other projects to support the new dependency version can come in a different commit. You only run into trouble when you've set up your projects to always use the latest version of their dependencies. That's a recipe for disaster.