Real Talk JavaScript
Smaller 20logo

Dive into JavaScript and Web development stories with hosts John Papa, Ward Bell, and Dan Wahlin.

A weekly podcast where we tackle the challenges facing Web developers today and invite expert guests on the show to share their experience solving concrete problems while building real Web applications.

Listen for practical insights and honest talk about the topics you are facing today, with Real Talk JavaScript.

  1. Thumb 1545522054 artwork
  2. Thumb 1545521816 artwork
  3. Thumb 1545106785 artwork
  4. Thumb 1544491785 artwork
  5. Thumb 1543891803 artwork
  6. Thumb 1543269293 artwork

    Episode 9: RxJS with Tracy Lee

    John and Ward talk with core RxJS team member, Tracy Lee. Tracy shares the direction of RxJS, who is using it, and some inside tips on how to learn RxJS and common pitfalls.

  7. Thumb 1542580373 artwork
  8. Thumb 1542101798 artwork

    Episode 7: Custom Web Components with Rob Wormald

    John, Dan and Ward talk with Rob Wormald about his views on where Custom Web Components are heading. Rob talks about Polymer, web components, how Angular and other frameworks approach web components, and where he thinks we should all head.

  9. Thumb 1541376440 artwork

    Episode 6: Upgrading JavaScript Apps with Sam Julien

    John and Ward talk with Sam Julien about how he approaches upgrade to Angular and other JavaScript applications.

    Sam spent the last few years at a non-profit with a series of refactors and migrations/rewrites with his team. For example: - Rewriting the C# API, first to unit of work (complete rewrite), then refactoring to CQRS - Adding ES6, followed by TypeScript, to the AngularJS front ends - Migrating the front ends from Gulp to Webpack and from Bower to npm - ngUpgrade (still in process when I left) - Determining whether to update to Webpack 4 or move to the CLI later - Several large data structure refactor projects initiated by the business that affected the entire stack (from SQL to Angular)

    They 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.

    I 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).

  10. Thumb 1540848475 artwork
View Older Episodes