008 jsAir - JavaScript Debugging with Alex Liu, Todd Gardner, and Yunong Xiao

JavaScript Air - Un pódcast de Kent C. Dodds

Categorías:

JavaScript Debugging with Alex Liu, Todd Gardner, and Yunong XiaoDescription:JavaScript has a pretty interesting debugging story. The developer tools of your browser of choice and the various tools and IDEs for debugging Node or mobile development make for a really interesting topic.Show sponsors:Egghead.io - Bite-sized web development video trainingFrontend Masters - Expert front-end training{Track:js} - JavaScript Error MonitoringWallaby.js - Realtime code coverageCodecov.io - Code coverage done rightFluent - Web development trainingLinks, Picks, and Tips:Alex LiuTips: Always think about Errors and error handling as part of the design and spec from day one and Understand the abstractions you use, especially when it comes to ErrorsPicks: VError, bunyan, restify-errors, and Overheard - VS Code debugger is greatTodd GardnerLinks: TrackJS for debugging non-chrome platforms, Charles Web Debugging Proxy, and Fiddler ProxyPicks: JavaScript Error Monitoring, JavaScript Forensics Talk, Amazing Conference in Oslo, Afterparty conference, Author: Ken Follett. Pillars of the Earth and a World Without End, and Conference SatireYunong XiaoLinks: mdb v8, Node post mortem debugger, Debugging Node.js in Prod, Flamegraphs, Flamegraphs with Node, Restify, Observable Rest Framework, and Debugging NodeTips: Use the Scientific Method, Error Types and JSON Parse, Error Handling in Node.js, JSON Logging Lib, and Observable Async libPicks: Bojack Horseman, ReactiveSocket, and Wish You Were HereBrian LonsdorfLinks: Elm’s debugger and Free Monad graphTips: Algebraic data structures like Either, Task, and Maybe ensure we handle all errors. The errors are pushed to the caller where it’s easy to see., In node, you can overwrite Obj.prototype.inspect to display a custom string when console.log-ing., and Learn to use debugger; in the browser.Picks: Bodil Stokke Generators and Profunctor LensesKyle SimpsonTips: Chrome CPU Throttling, OSS your code early. Don’t wait until “it’s good enough for others”, because then you’ve waited too long. OSS is about collaboration and improvement, not promotion of already-finished code., and Start with libraries and frameworks as you rapidly develop/evolve/explore a project. But as it matures, try to build time in for refactoring to reduce/remove those pieces. You don’t need them permanently. The best code is the code that’s exactly what’s needed, no more, no less.Picks: About the new ‘createImageBitmap(..)’ API and also ‘requestIdleCallback(..)’, Chris & Getify Make A Game (part 1) tutorial on simple game making with me and @chriscoyier, and Cloud Sweeper my first casual web game, OSS code releasedKent C. DoddsLinks: Async checkbox in Chrome DevTools and Managing Memore Garbage Collection in NodeJS - Egghead.io lessonTips: Teach to learn. Force yourself to teach.Picks: What’s new in Webpack 2 and Debugging JavaScript (Chrome DevTools)About JavaScript Air:JavaScriptAir is the live broadcast podcast all about JavaScript hosted by egghead.io instructor Kent C. Dodds. Please visit the JavaScript Air website (javascriptair.com) to see upcoming and past episodes. Go to suggest.jsair.io to suggest topics and guests for the show. Go to feedback.jsair.io to provide feedback on this and other episodes. Also be sure to follow JavaScript Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well.

Visit the podcast's native language site