After the Angular 1-to-2 letdown, this is a refreshing commitment to keeping a stable API.
It illustrates the use of
- feature toggles to reduce merge conflicts
- TDD for api coverage
- regression logging for faster feedback loop
- coverage chart for motivation
- staggered rollout and A/B testing with an eye on product metrics for migration issues
Thanks for sharing!
After the Angular 1-to-2 letdown, this is a refreshing commitment to keeping a stable API.