Imagine your legacy production Ruby application is highly dependent on a third-party API — until you learn your vendor deprecates your current connection. What do you do when you’re forced to make a change? Accept the challenge by embracing abstractions, switching libraries, feature flags, edge-case testing while developing new features. Game on.
Focuses on: Famous example of third-party dependencies that have broken application; Abstracting the API interaction; Utilizing Ruby switching libraries; Feature flagging; Testing for edge cases (QA & customer service); and much more!