4 ms·
One strategy that I've seen work for this kind of deep architectural change is to write the new system, then write a shim that provides a compatibility layer (h
by azernik 11y ago
One strategy that I've seen work for this kind of deep architectural change is to write the new system, then write a shim that provides a compatibility layer (however hacky and ugly) to emulate the old system. This lets you test the new system without then having to also test everything that the system interacts with. And then, start replacing usages of the shim with direct interaction with the newer prettier system.
Think the win32 to NPAPI transition.
- leonardinius 11y agoI believe you are describing http://www.martinfowler.com/bliki/StranglerApplication.html http://www.martinfowler.com/bliki/StranglerApplication.html and particularly http://www.martinfowler.com/bliki/AssetCapture.html http://www.martinfowler.com/bliki/AssetCapture.html
- azernik 11y agoYup! Loved that article when I first saw it on HN - I felt it described well a lot of upgrade projects undertaken at my then-employer.