The panelists talk about design patterns in JavaScript with Addy Osmani

Sponsors:

• Netlify
• Sentry use the code “devchat” for $100 credit
• Clubhouse

Panel:

Charles Max Wood

Special Guest: Brady Gaster

In this episode, Chuck talks with Brady Gaster about SignalR that is offered through Microsoft. Brady Gaster is a computer software engineer at Microsoft and past employers include Logical Advantage, and Market America, Inc. Check out today’s episode where the two dive deep into SignalR topics.

Links:

• Vue
• jQuery
• Angular
• C#
• Chuck’s Twitter
• SignalR
• SignalR’s Twitter
• GitHub SignalR
• Socket.io
• Node-SASS
• ASP.NET SignalR Hubs API Guide – JavaScript Client
• SignalR.net
• Real Talk JavaScript
• Parcel
• Brady Gaster’s Twitter
• Brady Gaster’s GitHub
• Brady Gaster’s LinkedIn

Picks:

Brady

• Team on General Session
• Korg
• SeaHawks
• Brady’s kids
• Logictech spot light
• AirPods

Charles

• Express VPN
• Hyper Drive
• J5 ports and SD card readers
• Podwrench

Sponsors

• Triplebyte $1000 signing bonus
• Sentry use the code “devchat” for $100 credit
• CacheFly

Panel

• Aaron Frost
• AJ O’Neal
• Joe Eames
• Aimee Knight
• Chris Ferdinandi

Joined by special guest: James Shore

Episode Summary

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

Links

• Agile
• Angular
• API
• CRC cards (class responsibility collaborators)
• Ember
• IntelliJ
• NPM
• React
• Redux
• Scrum
• Waterfall
• XJS

Picks

AJ O’Neal:

• Spiderman: Into the Spider-Verse
• Pre-gap tracks album list
• QuickChip remover alloy

Aimee Knight:

• Puns.dev
• Bouldering

James Shore:

• Spiderman: Into the Spider Verse
• Pandemic Legacy

Aaron Frost:

• Easter Candy, especially
  • Nerd Jelly beans
  • Cadbury Mini Eggs
• Fun D&D moments

Joe Eames:

Chronicles of Crime board game

Sponsors

• Datadog

• Sentry use code “devchat” for 2 months free

Panel

• Aimee Knight

• Chris Ferdinandi

• Joe Eames

• AJ O’Neal

• Charles Max Wood

With Special Guests: Josh Thomas and Mike Hartington

Episode Summary

Today’s guests Josh Thomas and Mike Hartington are developers for Ionic, with Josh working on the open source part of the framework on Ionic. They talk about their new compiler for web components called Stencil. Stencil was originally created out of work they did for Ionic 4 (now available for Vue, React, and Angular) and making Ionic 4 able to compliment all the different frameworks. They talk about their decision to build their own compiler and why they decided to open source it. Now, a lot of companies are looking into using Stencil to build design systems

The panel discusses when design systems should be implemented. Since Ionic is a component library that people can pull from and use themselves, Jeff and Mike talk about how they are using Stencil since they’re not creating a design system.

The panel discusses some of the drawbacks of web components. They discuss whether or not Cordova changes the game at all. One of the big advantages of using Stencil is the code that is delivered to a browser is generated in such a way that a lot of things are handled for you, unlike in other systems.The panelists talk about their thoughts on web components and the benefits of using a component versus creating a widget the old fashioned way. One such benefit of web components is that you can change the internals of how it works without affecting the API. Josh and Mike talk about some of the abilities of Stencil and compare it to other things like Tachyons. There is a short discussion of the line between frameworks and components and the dangers of pre optimization. If you would like to learn more about Stencil, go to stenciljs.com and follow Josh and Mike @Jtoms1 and @mhartington.

Click here to cast your vote NOW for JavaScript Jabber - Best Dev Podcast Award

Links

• Building Design Systems book

• Stencil

• Cordova

• Shadow DOM

• Tachyons 

• Ionic 4

Follow DevChat on Facebook and Twitter

Picks

Aimee Knight:

• What Does Debugging a Program Look Like?

AJ O’Neal:

• Legend of Zelda: Link’s Awakening

• Neon Genesis Evangelion soundtrack

• Prettier

Chris Ferdinandi:

• Kindle Paperwhite

• Company of One

Charles Max Wood:

• Ladders with feet

• Lighthouse

• Acorns

Joe Eames:

• Moment.js

• How To Increase Your Page Size by 1500% article

• Day.js

Josh Thomas:

• Toy Story 4

Mike Hartington:

• Building Design Systems

• Youmightnotneed.com

Kaelig Deloumeau-Prigent is a self taught web developer from west France. He has worked for BBC, The Guardian, and The Financial Times in the UK. He has also worked in the US for SalesForce and currently works for Shopify on their Polaris design system. Shopify has multiple design systems, and Polaris is open source. Today the panel is talking about design systems and developer tooling around design systems. 

To begin, Kaelig explains what a design system is. A design system is all of the cultural practices around design and shipping a product. It includes things like the words, colors, spacing grid system, and typography, plus guidance on how to achieve that in code. The panelists discuss what has made design systems so popular. Design systems have been around for a while, but became popular due to the shift to components, which has been accelerated by the popularity of React. The term design system is also misused by a lot of people, for it is much more than having a Sketch file. 

Next, they talk about whether design systems fall under the jurisdiction of a frontend developer or web designers. Kaelig has found that a successful design system involves a little bit of everyone and shouldn’t be isolated to one team. They talk about what the developer workflow looks like in a design system. It begins with thinking of a few common rules, a language, and putting it into code. As you scale, design systems can become quite large and it’s impossible for one person to know everything. You either give into the chaos, or you start a devops practice where people start to think about how we build, release, and the path from designer’s brain to production.

The panelists then talk about how to introduce a design system into a company where there are cultural conflicts. Kaelig shares his experience working with SalesForce and introducing a design system there. They discuss what aspects of a design system that would make people want to use it over what the team is currently doing. Usually teams are thankful for the design system. It’s important to build a system that’s complete, flexible, and extensible so that you can adapt it to your team. A good design system incorporates ‘subatomic’ parts like the grid system, color palette, and typography, referred to as design tokens. Design systems enable people to take just the bits of the design system that are interesting to them and build the components that are missing more easily. 

The conversation turns to the installation and upgrade process of a design system. Upgrading is left up to the customer to do on their own time in most cases, unless it’s one of the big customers. They talk about the role of components in upgrading a design system. Kaelig talks about the possibility of Shopify transitioning to web components. Kaelig shares some of his favorite tools for making a design system and how to get started making one. A lot of design teams start by taking a ton of screen shots and looking at all the inconsistencies.Giving them that visibility is a good thing because it helps get everyone get on the same page. The panelists talk about the role of upper management in developing components and how to prioritize feature development. Kaelig talks about what drives the decision to take a feature out. The two main reasons a feature would be removed is because the company wants to change the way things are done and there’s a different need that has arisen. The show concludes by discussing the possibility of a design system getting bloated over time. Kaelig says that Design systems takes some of the burden off your team, help prevent things from getting bloated, allow you to ship less code.

Panelists

• Chris Ferdinandi

• Aimee Knight

• Steve Emmerich

With special guest: Kaelig Deloumeau-Prigent

Sponsors

• Sustain Our Software

• Sentry use the code “devchat” for 2 months free on Sentry’s small plan

• Adventures in Blockchain

Links

• Shopify Polaris

• Bootstrap

• React

• Sketch.ui

• Figma.ui 

• CSS

• StoryBook

• ESLint

• Jest

• Ensign

• Webpacker

Follow DevChatTV on Facebook and Twitter

Picks

Steve Emmerich:

• CedarWorks play beds 

• Azure’s container instances

Aimee Knight:

• Awesome Actions for Github

Chris Ferdinandi:

• Free Meek docuseries

• Simplicity: Part 2 by Bastian Allgeier

Kaelig Deloumeau-Prigent:

• Dependabot

• Ink by Vadim Demedez

• Follow Kaelig on Twitter @kaelig

In this episode of JavaScript Jabber the panelists and guest delve into the advantages of the shadow dom, transitioning from polymer js polyfills to native web components when moving for SAP UI to UI5, which works within React, Vue, Angular, and others.

Panel

• AJ O’Neal
• Aimee Knight
• Steve Edwards
• Dan Shappir

Guest

• Peter Müßig
• Follow Peter on Twitter > @pmuessig, Github

Sponsors

• Taiko, free and open source browser test automation

____________________________________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• OpenUI5
• Home - SAPUI5 SDK

Picks

AJ O’Neal:

• Vinyl Clocks
• Acrylic Stand
• AJ's YouTube Channel (AMA)

Aimee Knight

• Announcing Div Ops as the Slack and Reddit communities

Steve Edwards

• Today on Pearls Before Swine - Comics by Stephan Pastis

Dan Shappir

• The Wixing Street Interview | Facts about Wixing in Germany
• Wix.com werbung | versuch nicht zu lachen
• UI5 Web Components

Peter Müßig

• JavaScript Jabber

Follow JavaScript Jabber on Twitter > @JSJabber

Schwartz, Judith D., author

Rieth, Michael

Ganguli, Prabuddha

Designing nanoparticle systems for catalysis (2018 : London).

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Online Resource

Mathew, Bincy, 1979- author

Eyl, Jennifer, author

Boring, M. Eugene, author

Hall, Crystal L., author

Plenert, Gerhard Johannes, author

Schniederjans, Marc J., author

Allen, David T

Robbins, Stephen P., 1943- author

Sherwin, David, author

Stull, Edward. author

Frisendal, Thomas. author

Geraldi, Joana G., 1979- author

Pande, Peter S

Interview with Christopher R. Cederroth, PhD, author of Association of Genetic vs Environmental Factors in Swedish Adoptees With Clinically Significant Tinnitus

Interview with Trevor J. Royce, MD MS MPH, author of Analysis of Price Transparency via National Cancer Institute–Designated Cancer Centers’ Chargemasters for Prostate Cancer Radiation Therapy

Interview with Schuyler Jones, MD, and Adrian F Hernandez, MD, MHS, authors of Rationale and Design of the Aspirin Dosing—A Patient-Centric Trial Assessing Benefits and Long-term Effectiveness (ADAPTABLE) Trial