Australia. Climate Change Authority, author, issuing body

Hahn, Matthew William, 1975- author

Rodríguez Eugenio, Natalie, author

Nickel/Cobalt Pressure Leaching & Hydrometallurgy Forum (4th : 1998 : Perth, W.A.)

Rodriguez, Esther

Bulatovic, Srdjan M

D'Aloya de Pinilla, Anna, author

The panelists talk to Dave Nugent about organizing conferences and Meetups.

The panel discusses Share.js with Joseph Gentle

Check out React Remote Conf

01:56 - Valeri Karpov Introduction

• Twitter
• GitHub
• Blog
• JavaScript Jabber Episode #92: The MEAN Stack with Ward Bell and Valeri Karpov

02:17 - Booster Fuels

03:06 - ES2015 Generators

• The 80/20 Guide to ES2015 Generators by Valeri Karpov
• co

05:47 - try-catch

07:49 - Generator Function vs Object

• The Fibonacci Sequence

10:39 - Generator Use Cases

12:02 - Why in ES6 would they come out with both native promises and generators?

• Koa

14:04 - yield star and async await

17:06 - Wrapping a Generator in a Promise

19:51 - Testing

20:56 - Use on the Front-end

22:14 - The 80/20 Guide to ES2015 Generators by Valeri Karpov and Tech Writing

• nightmare
• Professional AngularJS

Picks

Why and How Testing Can Make You Happier (Aimee)
Pitango Gelato (Aimee)
The Primal Blueprint by Mark Sisson (Chuck)
The Primal Blueprint 21-Day Total Body Transformation (Chuck)
acquit (Valeri)
nightmare (Valeri)
now (Valeri)
The 80/20 Guide to ES2015 Generators by Valeri Karpov (Valeri)

Panel:

• Charles Max Wood
• Aimee Knight
• AJ ONeal

Special Guests: Dotan Nahum

In this episode, the JavaScript Jabber panelists discuss Hygen with Dotan Nahum. Dotan has worked within open source community, where he created Hygen. They talk about what Hygen is, how it came to be, and code generators in general. He was inspired by the Rails generator to create his own generator and took his inspiration from 12 years prior to creating Hygen. They also touch on how to share generators in separate packages and much more!

In particular, we dive pretty deep on:

• Dotan intro
• What is Hygen?
• Code generators
• Rails in 2006
• Ruby on Rails 15-minute blog video
• PHP and Python
• Carried Rails wow moment with him into creating Hygen
• Wanted Rails generators everywhere
• Can you also modify files?
• Took the good things from Rails generator
• The fact that front-end apps have architecture is new
• Redux
• The solution of generating code
• A component is a ray of files and assets
• JavaScript gives you great freedom
• A standardized way of doing components
• GraphQL
• Everything lives in the “day job” project
• How the Hygen template is formatted
• Can have a shell action
• Is there a way to share generators in a separate package?
• Go
• And much, much more!

Links:

• Hygen
• Rails
• Ruby on Rails 15-minute blog video
• Python
• Redux
• JavaScript
• GraphQL
• Go
• @jondot
• Dotan’s GitHub
• Dotan’s Medium

Picks:

Charles

• Fluent Conf
• Hot Jar
• DevChat.tv
• Ethereum

Aimee

• Deep-copying in JavaScript

AJ

• Let’s Encrypt
• Nintendo Switch
• Breath of the Wild

Dotan

• asdf
• Brew Cask

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

This My JavaScript Story episode is a discussion with Kaelig Deloumeau-Prigent. Kaelig works on the Polaris design system from Shopify. We walk through his journey into programming, HTML, and CSS. We wander through is career until he was building design systems at Shopify.

Host: Charles Max Wood

Joined By Special Guest: Kaelig Deloumeau-Pregent

Sponsors

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

• CacheFly

___________________________________________________________________________________________

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

___________________________________________________________________________________________

Links

• JSJ 397: Design Systems with Kaelig Deloumeau-Prigent

• Design Tokens Community Group

• JSJ 388: Functional Programming with Brian Lonsdorf

• Polaris

Picks

Kaelig Deloumeau-Prigent:

• The Courage to Be Disliked

Charles Max Wood:

• The Name of The Wind

Stadler, Nurit

Deutscher, Penelope, 1966-

Ellwanger, Steven J., 1971-

Pruitt, Lesley J

This study develops and validates a quantitative method to predict the pulmonary to systemic flow ratio in patients with congenital heart disease from chest radiographs using deep learning.

Lowering low-density lipoprotein cholesterol (LDL-C) levels remains a mainstay of cardiovascular disease prevention, but gaps in treatment remain, even in persons with hypercholesterolemia and greatly elevated LDL-C levels. Although well-described gene variants in the apolipoprotein B (APOB), low-density lipoprotein receptor (LDLR), and proprotein convertase subtilisin/kexin type 9 (PCSK9) genes explain small but important fractions of monogenic hypercholesterolemia, recent attention has turned to prognostication of cardiovascular disease using polygenic risk scores (PRS) that incorporate common genetic variants derived from large-scale genome-wide association studies of lipid subfractions. Earlier PRS considered only variants with genome-wide significance, and newer studies have focused on methods that better capture the variance conferred by millions of variants, suggesting an ability to identify risk equivalent to monogenic mutations. There remains a gap in evidence from prospective observational studies or treatment trials regarding the appropriate placement of PRS in risk assessment and lipid treatment decisions relative to information on rare monogenic gene variants, particularly in multiethnic populations.

This cohort study uses the UK Biobank cohort data to compare the association of monogenic vs polygenic hypercholesterolemia with the risk of atherosclerotic cardiovascular disease among individuals with comparable levels of low-density lipoprotein cholesterol.

This essay describes a physician’s experience of the sudden, unexplained death of her brother and her family’s discovery of the genetic cause.

With the arrest of Tehsin Akhtar, thought to be Indian Mujahideen (IM) commander of India operations, security agencies have netted another big fish in the fight against terror.

Coen, Natasha Jeanne, author

This study uses mendelian randomization to estimate the associations between genetic variants related to reduced HMG-CoA reductase activity and epithelial ovarian cancer in the general population and in BRCA1/2 mutation carriers.