Preact, Performance, and the Future of Lightweight Frontends with Ryan Christian -JSJ 683

SponsorsTriplebyte offers a $1000 signing bonusSentry use the code “devchat” for $100 creditLinode offers $20 creditCacheFlyPanelAimee KnightAJ O’NealChris FerdinandiEpisode SummaryIn this episode of JavaScript Jabber, the panelists discuss each one’s definition of the term ‘pairing’ in programming, including factors like being remote or local, having different seniority levels and the various approaches of going about it in general. They talk about how valuable pairing is, in terms of benefiting the individual as well as how productive it is for the company or the overall business.The panel also discuss prototyping, pseudo-coding and the advantages and trade-offs involved in pair programming. They talk about their own experiences in which pairing had proven to be extremely beneficial and the ones where it went completely wrong, thereby helping listeners understand the dos and don’ts of the technique. In the end, they elaborate on what actually happens in pairing interviews and the overall hiring process while sharing anecdotes from their own lives.LinksFollow JavaScript Jabber on Devchat.tv, Facebook and Twitter.PicksChris Ferdinandi:Enso RingsVanilla JS ProjectsAJ O’Neal:Salt and Pepper Grinder setPeppercorn blendPink Himalayan saltAimee Knight:Enneagram testKittyramaSupport 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 Jun 20191h 4min

SponsorsTriplebyte offers a $1000 signing bonusSentry use the code “devchat” for $100 creditLinode offers $20 creditCacheFlyPanelAJ O’NealChris FerdinandiAimee KnightCharles Max WoodJoined by special guest: Mikeal RogersEpisode SummaryThis episode of JavaScript Jabber starts with Mikeal Rogers introducing himself and his work in brief. Charles clarifies that he wants to focus this show on some beginner content such as node.js basics, so Mikeal gives some historical background on the concept, elaborates on its modern usage and features and explains what “streams” are, for listeners who are starting to get into JavaScript. The panelists then discuss how languages like Go and Python compare to node.js in terms of growth and individual learning curves. Mikeal answers questions about alternate CLIs, package management, Pika, import maps and their effect on node.js, and on learning JavaScript in general. Chris, Charles and AJ also chip in with their experiences in teaching modern JS to new learners and its difficulty level in comparison to other frameworks. They wrap up the episode with picks.LinksMikeal on TwitterMikeal on GitHubFollow JavaScript Jabber on Devchat.tv, Facebook and Twitter.PicksChris Ferdinandi:Mozilla FirefoxArtifact ConferenceAimee Knight:A Magician Explains Why We See What’s Not ThereProgramming: doing it more vs doing it betterMikeal Rogers:The Future of the Web – CascadiaJS 2018Brave BrowserCharles Max Wood:PodwrenchSpecial Guest: Mikeal Rogers. Support 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 Mai 20191h 11min

SponsorsSentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus LinodePanelCharles Max WoodAimee KnightChris FerdinandiAJ O’NealJoe EamesEpisode SummaryToday the panel discusses the necessity of a front end framework. Overall, there is a consensus that frameworks are not necessary in all situations. They discuss the downsides of using frameworks, such as being restricted by the framework when doing edge development and the time required for learning a framework. They talk about the value of frameworks for learning patterns in programming. The panel delves into the pros and cons of different frameworks available. Joe shares a story about teaching someone first without a framework and then introducing them to frameworks, and the way it helped with their learning. One of the pros of frameworks is that they are better documented than manual coding. They all agree that it is not enough to just know a framework, you must continue to learn JavaScript as well. They talk about the necessity for new programmers to learn a framework to get a job, and the consensus is that a knowledge of vanilla JavaScript and a general knowledge of the framework for the job is important. New programmers are advised to not be crippled by the fear of not knowing enough and to have an attitude of continual learning. In the technology industry, it is easy to get overwhelmed by all the developments and feel that one cannot possibly learn it all. Charles gives advice on how to find your place in the development world. The show concludes with the panel agreeing that frameworks are overall a good thing and are valuable tools. LinksJWTAngularVueBackboneGoLangExpressReactReduxHyper HTML4eachPascalJQueryNpm.js Follow DevChat on Facebook and Twitter PicksCharles Max Wood:PodwrenchAimee Knight:How to Love Your Job and Avoid BurnoutSo Good They Can’t Ignore YouChris Ferdinandi:Vanilla JS toolkitThinksterArtifact ConferenceAJ O’Neal:Binary CocoaBinary Cocoa Slamorama KickstarterBinary Cocoa Straight 4RootSupport 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 Mai 20191h 14min

SponsorsTriplebyte offers a $1000 signing bonusSentry use the code “devchat” for $100 creditLinodeCacheFlyPanelAJ O’NealJoined by special guest: Sam SelikoffEpisode SummaryIn this episode of JavaScript Jabber, Sam Selikoff, Co-Founder at EmberMap, Inc. starts with giving a brief background about himself and his work followed by a discussion with AJ O’Neal about the Ember community. Sam mentions some of the biggest advantages in using Ember, and what it should and should not be used for. He explains the architecture of Ember apps, addresses some of the performance concerns and then dives into Octane in detail. He talks about a bunch of Ember components, compiler compatibility, relative weight of Ember apps compared to other frameworks, the underlying build system, and security considerations. Sam then helps listeners understand the usage of ES6 classes and decorators in Ember at length. At the end, they discuss component rendering and element modifiers and move onto picks.LinksSam’s websiteSam on TwitterSam on GitHubFollow JavaScript Jabber on Devchat.tv, Facebook and Twitter.PicksAJ O’Neal:Good Mythical Morning - YouTubeSam Selikoff:The Man In the High Castle  Tailwind CSSSpecial Guest: Sam Selikoff. Support 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 Mai 201952min

SponsorsTriplebyte offers a $1000 signing bonusSentry use the code “devchat” for $100 creditLinodeCacheFlyPanelCharles Max WoodAimee KnightAJ O’NealAaron FrostJoe EamesJoined by Special Guest: Gareth McCumskeySummaryGareth McCumskey introduces JAMstack and serverless. He goes into great detail on how it works. Aimee Knight and Aaron Frost voice their concerns about going serverless. Aimee thinks it feels dirty. Aaron has concerns about the code, is it actually easier, what use cases would he use it for, and does it actually save money. Gareth addresses these concerns and the rest of the panel considers the positive and negatives of using JAMstack and serverless. Charles Max Wood asks for specific use cases; Gareth supplies many uses cases and the benefits that each of these cases.Linkshttp://herodev.com/https://thinkster.io/https://jamstack.org/https://www.mongodb.com/cloud/stitchhttps://expatexplore.com/https://serverless.com/https://www.cloud66.com/https://aws.amazon.com/dynamodb/https://twitter.com/garethmcchttps://www.facebook.com/javascriptjabberhttps://twitter.com/JSJabberPicksCharles Max Wood:Join the mailing listWatch out for new podcastsSend me defunct podcasts you love chuck@devchat.tvAimee Knight:Productivity Isn’t About Time Management. It’s About Attention Management.Quest Nutrition Protein BarsAJ O’Neal:Distant Worlds: Music from Final Fantasy by Nobuo UematsuLegend Of Zelda Concert 2018 Original Soundtrack by Never Land Orchestra  How to Diagnose and Fix Everything Electronic by Michael Jay Geier  Aaron Frost:The Go-Giver, Expanded Edition: A Little Story About a Powerful Business IdeaGareth McCumskey:https://www.finalfantasyxiv.com/Steam Play on LinuxJoe Eames:Expanding your horizonsSeven Languages in Seven Weeks: A Pragmatic Guide to Learning Programming LanguagesSeven More Languages in Seven Weeks: Languages That Are Shaping the Futurehttps://elm-lang.org/Special Guest: Gareth McCumskey. Support 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 Mai 20191h 10min

SponsorsSentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus PanelCharles Max WoodAimee KnightChris FerdinandiAJ O’NealJoe EamesJoined by Special Guest: Chris DeMarsEpisode Summary Special guest Chris DeMars is from Detroit, MI. Currently, he works for Tuft and Needle and is an international speaker, Google developer expert, Microsoft mvp, and web accessibility specialist. He comes from a varied work background, including truck driving and other non-tech jobs.    Today the panel discusses web accessibility for people with disabilities. According to a study done by WebAIM, 97.8% of homepages tested had detectable WCAG 2 failures. The panel discusses why web accessibility is doing so poorly. Chris talks about some of the biggest mistakes he sees and some very simple fixes to make sites more accessible. Chris talks about the importance of manual testing on screen readers and emphasizes that it is important to cover the screen to make sure that it really works with a screen reader. Chris talks about some of the resources available for those who wish to increase accessibility on their sites.   The team discusses tactics for prioritizing accessibility and if there is a moral obligation to make sites accessible to those with disabilities. Chris talks about his experience making accessibility a priority for one of the companies he worked for in the past. They discuss the futue of legal ramifications for sites that do not incorporate accessibility, and what responsibility falls on the shoulders of people who regularly use assistive devices to notify companies of issues. They finish the show with resources available to people who want to learn more. LinksThe DOMSemantic markup writingsAlt attributeAxe by DeQue BootstrapAria lableWebAim study Follow DevChat on Facebook and Twitter PicksCharles Max Wood:LootCrateAimee Knight:Implementing Git in Python tutorialChris Ferdinandi:"Fighting Uphill" by Eric Bailey“The Web We Broke” by Ethan Marcotte AllBirds sneakers NewsletterAJ O’Neal:Golang Channel vs Mutex vs WaitGroupNobuo UematsuThe Best Way to Tin Enameled WireJoe Eames:Gizmos board gameThinkster.io accessibility course (not released yet)Chris DeMars:Dixxon Flannel CompanyAquis.com accessibility simulator Refactr accessibility workshop in June Follow Chris Special Guest: Chris DeMars. Support 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.

30 Apr 20191h 3min

SponsorsTriplebyte offers a $1000 signing bonusSentry use the code “devchat” for $100 creditCacheFlyPanelAJ O’NealJoe EamesAimee KnightCharles Max WoodChris FerdinandiJoined by Special guest: Nicholas ZakasSummaryNicholas Zakas discusses the overuse of JavaScript and the underuse of HTML and CSS. The panel contemplates the talk Nicholas Zakas gave 6 years ago about this very same topic and how this is still a problem in the development community. Nicholas expounds on the negative effects overusing Javascript has on web applications and the things that using HTML and CSS do really well. The panel talks about the need for simplicity and using the right tool to build applications. Nicholas recommends the methods he uses to build greenfield applications and to improve existing applications.Linkshttps://www.youtube.com/watch?v=li4Y0E_x8zEhttps://www.slideshare.net/nzakas/enough-withthejavascriptalreadyhttps://twitter.com/slicknethttps://humanwhocodes.com/https://www.facebook.com/javascriptjabberhttps://twitter.com/JSJabberPicksChris Ferdinandi:The Umbrella Academy Official Trailerhttps://github.com/features/actionsAJ O’Neal:Jurassic ParkTerminator 2E6000 adhesiveAimee Knight:https://www.reebok.com/us/reebok-legacy-lifter/BD4730.htmlhttps://www.holloway.com/g/equity-compensationCharles Max Wood:https://podfestexpo.com/http://charlesmaxwood.com/https://www.11ty.io/https://www.netlify.com/Joe Eames:https://www.mysteryscenemag.com/blog-article/5905-tom-straw-the-author-behind-castleRichard Castle bookshttps://vanillajslist.com/Nicholas Zakas:The Power of Full Engagement: Managing Energy, Not Time, Is the Key to High Performance and Personal Renewal by Jim Loehr and Tony Schwartzhttps://opencollective.com/eslintSpecial Guest: Nicholas C. Zakas. Support 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.

23 Apr 20191h 8min

SponsorsTriplebyte $1000 signing bonusSentry use the code “devchat” for $100 creditCacheFlyPanelAaron FrostAJ O’NealJoe EamesAimee KnightChris FerdinandiJoined by special guest: James ShoreEpisode SummarySpecial guest James Shore returns for another episode of JavaScript Jabber. Today the panel discusses the idea of evolutionary design. Evolutionary design comes from Agile development. It is based on the principles of continuous integration and delivery and test driven development. In short, evolutionary design is designing your code as you go rather than in advance.The panelists discuss the difficulties of evolutionary design and how to keep the code manageable.  James Shore introduces the three types of design that make up evolutionary design, namely simple design, incremental design, and continuous design. They talk about the differences between evolutionary design and intelligent design and the correlations between evolutionary design increasing in popularity and the usage of Cloud services. They talk about environments that are and are not conducive to evolutionary design and the financial ramifications of utilizing evolutionary design.The panelists talk about the difficulties of planning what is needed in code and how it could benefit from evolutionary design. James enumerates the steps for implementing evolutionary design, which are upfront design, reflective design, and refactoring . The team ends by discussing the value of frameworks and how they fit with evolutionary design.LinksAgileAngularAPICRC cards (class responsibility collaborators)EmberIntelliJNPMReactRedux ScrumWaterfallXJSPicksAJ O’Neal:Spiderman: Into the Spider-VersePre-gap tracks album listQuickChip remover alloyAimee Knight:Puns.devBoulderingJames Shore:Spiderman: Into the Spider VersePandemic LegacyAaron Frost:Easter Candy, especially Nerd Jelly beansCadbury Mini EggsFun D&D momentsJoe Eames: Chronicles of Crime board gameSpecial Guest: James Shore. Support 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.

16 Apr 20191h 2min