BROADCASTS.com

b'John and Ward talk with Sam Julien about how he approaches upgrade to Angular and other JavaScript applications. \\n\\nSam spent the last few years at a non-profit with a series of refactors and migrations/rewrites with his team. For example:\\n- Rewriting the C# API, first to unit of work (complete rewrite), then refactoring to CQRS\\n- Adding ES6, followed by TypeScript, to the AngularJS front ends\\n- Migrating the front ends from Gulp to Webpack and from Bower to npm\\n- ngUpgrade (still in process when I left)\\n- Determining whether to update to Webpack 4 or move to the CLI later\\n- Several large data structure refactor projects initiated by the business that affected the entire stack (from SQL to Angular)\\n\\nThey had to evaluate the risk of maintenance vs the risk of updating vs the risk of rewriting. They used a mix of determining the business impact, the technical debt, and developing proof of concepts to figure this out each time. \\n\\nI feel like this is a constant issue teams face, especially smaller teams that are not working for software companies (though software companies, of course, do this as well, but are perhaps more driven by end-user needs/sales).'