JavaScript Jabber

Panel: Charles Max WoodAJ O’NealAimee Knight Special Guests: Valeri Karpov In this episode, the panel talks with programmer, Valerie Karpov from Miami, Florida. He is quite knowledgeable with many different programs, but today’s episode they talk specifically about Async/Await and Promise Generators. Val is constantly busy through his different endeavors and recently finished his e-book, “Mastering Async/Await.” Check-out Val’s social media profiles through LinkedIn, GitHub, Twitter, and more.Show Topics:1:20 – Val has been on previous episodes back in 2013 & 2016.1:37 – Val’s background. He is very involved with multiple companies. Go checkout his new book! 2:39 – Promises generators. Understand Promises and how things sync with Promises. Val suggests that listeners have an integrated understanding of issues like error handling.3:57 – Chuck asks a question.6:25 – Aimee’s asks a question: “Can you speak to why someone would want to use Async/Await?”8:53 – AJ makes comments.10:09 – “What makes an Async/Await not functional?” – Val10:59 – “What’s wrong with Promises or Async/Await that people don’t like it?” - AJ11:25 – Val states that he doesn’t think there really is anything wrong with these programs it just depends on what you need it for. He thinks that having both gives the user great power.12:21 – AJ’s background is with Node and the Python among other programs.12:55 – Implementing Complex Business Logic.15:50 – Val discusses his new e-book.17:08 – Question from Aimee.17:16 – AJ answers question. Promises should have been primitive when it was designed or somewhat event handling.17:46 – The panel agrees that anything is better than Call Backs.18:18 – Aimee makes comments about Async/Await.20:08 – “What are the core principles of your new e-book?” – Chuck20:17 – There are 4 chapters and Val discusses, in detail, what’s in each chapter.22:40 – There could be some confusion from JavaScript for someone where this is their first language. Does Async/Await have any affect on the way you program or does anything make it less or more confusing in the background changes?24:30 – Val answers the before-mentioned question. Async/Await does not have anyway to help with this (data changes in the background).25:36 – “My procedural code, I know that things won’t change on me because it is procedural code. Is it hard to adjust to that?” – AJ26:01 – Val answers the question.26:32 – Building a webserver with Python. 27:31 – Aimee asks a question: “Do you think that there are cases in code base, where I would want to use Promises? Not from a user’s perspective, but what our preferences are, but actual performance. Is there a reason why I would want to use both or be consistent across the board?”28:17 – Val asks for some clarification to Aimee’s question.29:14 – Aimee: “My own personal preference is consistency. Would I want to use Promises in ‘x’ scenario and/or use Async/Await in another situation?”32:28 – Val and AJ are discussing and problem solving different situations that these programs33:05 – “When would you not want to use Async/Await?” – AJ33:25 – Val goes through the different situations when he would not use Async/Await. 33:44 – Chuck is curious about other features of Async/Await and asks Val.36:40 – Facebook’s Regenerator 37:11 – AJ: “Back in the day, people would be really concerned with JavaScript’s performance even with Chrome.” He continues his thoughts on this topic.38:11 – Val answers the AJ’s question.39:10 – Duck JS probably won’t include generators.41:18 – Val: “Have anyone used Engine Script before?” The rest of the panel had never heard of this before.42:09 – Windows Scripting Host 42:56 – Val used Rhino in the past.43:40 – Val: “Going back to the web performance question...”47:08 – “Where do you see using Async/Await the most?” – Chuck47:55 – Val uses Async/Await for everything on the backend because it has made everything so easy for him.48:23 – “So this is why you really haven’t used Web Pack?” – AJ49:20 – Let’s go to Aimee’s Picks!50:18 – AJ’s story, first, before we get to Promises.54:44 – Let’s transition to Promises Finally.54:53 – Val talks about Promises Finally.59:20 – PicksLinks:JavaScriptValeri Karpov’s GitHubValeri Karpov’s TwitterValeri Karpov’s LinkedInNew E-Book: Mastering Async/AwaitNodePythonWindows Scripting HostFacebook’s RegeneratorRhinoSponsors:Kendo UISentryDigital Ocean Picks:CharlesYouTube Video “IKEA” by CoultonConferenceAmazon Prime DayAimeeBlog Post ArticleAJIKEAhttps://ppl.familyValhttps://www.npmjs.com/package/servehttp://bit.ly/ultimate-skiinghttp://asyncawait.net/jsjabberNew E-Book: Mastering Async/AwaitSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

4 Sep 201846min

Panel: Joe EamesAimee KnightAJ O'NealJoe Eames Special Guests: Christine LeggeIn this episode, the JavaScript Jabber panel talks to Christine Legge about functional programming with Ramda. Christine is a front-end software engineer and just recently got a new job in New York working at Google. Ramda is a utility library in JavaScript that focuses on making it easier to write JavaScript code in a functional way. They talk about functional programming and what it is, using Ramda in Redux, and referential transparency. They also touch on why she first got into Ramda, compare Ramda to Lodash and Underscore, and more!In particular, we dive pretty deep on:Chirstine intro Works as a front-end software engineerWhat is Ramda? JavaScriptUtility library like Lodash and UnderscoreLodash and Underscore VS RamdaFunctional programmingRamda and Functional programming as a mindsetRamda at ZenHubRamda with Redux and ReactWhat is referential transparency?Why would you use Ramda VS Lodash or Underscore?Why she first got into RamdaDidn’t always want to be a programmerBackground in MathLearning functional programming as a new programmerErlangDrRacket and JavaRamda makes it easy to compose functionsCreating clean and reusable codeHow do you start using Ramda?And much, much more! Links:RamdaLodashUnderscoreZenHubReduxReactErlangDrRacket@leggechrChirstine’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesHome Depot Tool RentalPodcast MovementCESVRBOAimeeApple Cider VinegarJeremy Fairbank Talk – Practical Functional ProgrammingAJGoat’s MilkJoeTopgolfFramework SummitChristineDan ManganReply All PodcastSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

28 Aug 201855min

Panel:Charles Max WoodJoe Eames Special Guests: AJ O'NealIn this episode, the JavaScript Jabber panel talks to AJ O'Neal about Greenlock and LetsEncrypt. LetsEncrypt is a brand name and is the first of its kind in automated SSL and Greenlock does what Certbot does in a more simplified form. They talk about what led him to create Greenlock, compare Greenlock to Certbot, and what it’s like to use Greenlock. They also touch on Greenlock-express, how they make Greenlock better, and more!In particular, we dive pretty deep on:Greenlock and LetsEncrypt overviewLetsEncrypt is free to get your certificateWhy Charles uses LetsEncryptWildcard domainsCertbotWhy he originally created GreenlockWorking towards home serversWanted to get HTTP on small devicesManages a certificate directoryGreenlock VS CertbotGreenlock can work stand aloneThe best use case for GreenlockExcited about how people are using his toolWhat is it like to use Greenlock?Working on a desktop clientGreenlock-expressAcme serversCAA recordMaking Greenlock better by knowing how people are using itUsing Greenlock-expressLet's Encrypt v2 Step by Step by AJAnd much, much more!Links:LetsEncryptGreenlockCertbotGreenlock-expressAcme serversLet's Encrypt v2 Step by Step by AJ@coolaj86coolaj86.comAJ’s GitGreenlock.js Screencast SeriesGreenlock.js PatreonSponsorsKendo UISentryDigital OceanPicks:CharlesTake some time offAJOverClocked RecordsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

21 Aug 201855min

Panel: Joe EamesAimee KnightAJ ONeal Special Guests: Tom DaleIn this episode, the JavaScript Jabber panel talks to Tom Dale about Ember 3.0 and the future of Ember. Tom is the co-creator of Ember and is a principle staff engineer at LinkedIn where he works on a team called Presentation Infrastructure. They talk about being in the customer service role, having a collaborative culture, and all the information on Ember 3.0. They also touch on the tendency towards disposable software, the Ember model, and more!In particular, we dive pretty deep on:How Joe met TomProgrammers as rule breakersThe pressure to conformTom introStaff engineer at LinkedInCustomer service roleHaving a way to role improvements out to a lot of different peopleJavaScript and Ember at LinkedInHaving a collaborative cultureAll about Ember 3.0Banner feature – there is nothing newCracked how you develop software in the open source world that has longevityMajor competition in Backbone previouslyThe Ember community has never been more vibrantTendency towards disposable softwareThe idea of steady iteration towards improvementThe Ember modelBeing different from different frameworksEmber adoption ratesPython 3Valuable from a business perspective to use EmberEmber community being friendly to newbiesHow much Ember VS how much JavaScript will a new developer have to learn?And much, much more!Links:EmberLinkedInJavaScriptBackbonePython@tomdaletomdale.netTom’s GitHubSponsorsKendo UISentryDigital OceanPicks:JoeFramework SummitJayneReact sent Evan You a cakeAimeeMaker's Schedule, Manager's Schedule by Paul GrahamAJJames VeitchTomJavaScript Tech TalkDrake’s TiesMelissa Watson Ellis at Hall MaddenSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

14 Aug 201857min

Panel: Aimee KnightJoe EamesAJ ONeal Special Guests: Jeremy FairbankIn this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more!In particular, we dive pretty deep on:Jeremy introWorks for Test DoubleWhat he means by “remote”What is Test Double?They believe software is broken and they are there to fix itHis talk - Practical Functional ProgrammingThe 6 things he talked about in his talkPractical aspects that any software engineer is going to deal withPurity and the side effects of programming in generalHard to follow codeImperative VS declarative codeCode breaking unexpectedlyMutable data VS immutable dataThe idea of too much codeCombining multiple functions together to make more complex functionsFunction compositionElm, Elixir, and F#Pipe operatorScary to refactor codeStatic typesThe idea of nullThe theory of unit testingIs functional programming the solution?His approach from the talkAnd much, much more!Links:Test DoubleHis talk - Practical Functional ProgrammingElmElixirF#@elpapapollojeremyfairbank.comJeremy’s GitHubJeremy’s YouTubeSponsorsKendo UISentryDigital OceanPicks:AimeeAmerican DollarForce with leaseAJSuperfightJoeThe 2018 Web Developer Roadmap by Brandon MorelliSvelteJeremyProgramming ElmThe Secrets of Consulting by Gerald M. WeinbergConnect.TechSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

7 Aug 201828min

Panel: Charles Max WoodJoe EamesAimee Knight Special Guests: Kent BeckIn this episode, the JavaScript Jabber panel talks to Kent Beck. Kent left Facebook 4 months ago after working for them for 7 years and is now self-unemployed so that he can decompress from the stressful environment that he was a part of for so long. He now travels, writes, creates art, thinks up crazy programming ideas, and is taking a breather.  They talk about what he did at Facebook, what his coaching engagement sessions consisted of, and the importance of taking time for yourself sometimes. They also touch on what he has learned from his experience coaching, how to create a healthy environment within the workplace, and more!In particular, we dive pretty deep on:Kent intro/updateRuby Rogues Episode 23Worked at Facebook for 7 yearsWhat were you doing at Facebook?Unique culture at FacebookHis strengths as a developer didn’t match with the organization’sCoaching developersTDD and PatternsAdvantages as an old engineerWhat did coaching engagement consist of?Takes time to build trustDischarging shameNeed permission to take care of what you need toBeing at your best so you can do your best workVacation in placeWhat have you learned in your time working with people?The nice thing about coachingEveryone is differentHow do we create a healthy environment within the workplace?Mentor in Ward CunninghamWhat is it costing us?Why did you decide to leave?And much, much more!Links:Ruby Rogues Episode 23@KentBeckkentbeck.comKent’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesThe Five Dysfunctions of a Team by Patrick LencioniCrucial Accountability by Kerry PattersonAimeen-backJoeTest Driven Development: By Example by Kent BeckKentThe Field Guide to Understanding 'Human Error' by Sidney DekkerConspiracy: Peter Thiel, Hulk Hogan, Gawker, and the Anatomy of Intrigue by Ryan HolidaySupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

31 Juli 20181h 6min

Panel: Charles Max WoodAJ ONeal Special Guests: Kurt MackeyIn this episode, the JavaScript Jabber panel talks to Kurt Mackey about Fly.io. At Fly.io, they are "building a JavaScript platform that gives you the power to build your own CDN." They talk about how Fly.io came to fruition, how CDN caching works, and what happens when you deploy a Fly app. They also touch on resizing images with Fly, how you actually build JavaScript platforms using Fly, and more!In particular, we dive pretty deep on:Fly.ioBuilding a programmable CDNHigh level overview of Fly.ioHow did this project come together?CDNs didn’t work with dynamic applicationsHas been working on this since 2008Extend application logic to the “edge”Putting burden of JavaScript “nastiest” onto the web serverFly is the proxy layerGetting things closer to visitors and usersCDN cachingCache APIsWriting logic to improve your lighthouse scoreHave you built in resizing images into Fly?Managing assets closer to the userCan you modify your own JavaScript files?What happens when you deploy a Fly appHaving more application logicDOM within the proxyGhostReact and GatsbyIntelligently loading client JavaScriptHow do you build the JavaScript platform?And much, much more!Links:Fly.ioJavaScriptGhostGatsbyReact@flydotio@mrkurtKurt at ARS TechnicaKurt’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesGitLabAJGiteaBlack PantherKurtPacket.netThe Three-Body Problem by Cixin LiuSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

26 Juli 20181h 3min

Panel: Charles Max Wood Special Guests: Vesa JuvonenIn this episode, the JavaScript Jabber panel talks to Vesa Juvonen about building SharePoint extensions with JavaScript. Vesa is on the SharePoint development team and is responsible for the SharePoint Framework, which is the modern way of implementing SharePoint customizations with JavaScript. They talk about what SharePoint is, why they chose to use JavaScript with it, and how he maintains isolation. They also touch on the best way to get started with SharePoint, give some great resources to help you use it, and more!In particular, we dive pretty deep on:Vesa introWhat is SharePoint?Has existed since 2009People either know about it and use it or don’t know what it isBaggage from a customization perspectiveWhy JavaScript developers?Modernizing developmentSharePoint FrameworkMicrosoft Ignite ConferenceIs there a market for it?System integratorsAngular Element and ReactReact for SharePoint Framework back-endSupports VueReact Round Up PodcastHow do you maintain isolation?What’s the best way to get started with SharePoint extensions?Office 365 Developer ProgramSharePoint documentationSharePoint YouTubeWhat kinds of extensions are you seeing people build?And much, much more!Links:SharePointJavaScriptSharePoint FrameworkMicrosoft Ignite ConferenceAngular ElementReactVueReact Round Up PodcastOffice 365 Developer ProgramSharePoint documentationSharePoint YouTube @OfficeDev@vesajuvonenVesa’s blogVesa’s GitHub@SharePointSponsorsKendo UISentryDigital OceanPicks:CharlesZig ZiglarConversations with My Dog by Zig ZiglarPimsleur Lessons on AudibleVesaArmada by Ernest ClineSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

17 Juli 201831min