JSJ 397: Design Systems with Kaelig Deloumeau-Prigent

JSJ 397: Design Systems with Kaelig Deloumeau-Prigent

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-PrigentSponsorsLinks Follow DevChatTV on Facebook and Twitter PicksSteve Emmerich:Aimee Knight:Chris Ferdinandi:Kaelig Deloumeau-Prigent:Special Guest: Kaelig Deloumeau-Prigent.

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Episoder(735)

JSJ 315: The effects of JS on CSS with Greg Whitworth

JSJ 315: The effects of JS on CSS with Greg Whitworth

Panel: AJ O’NealAimee Knight Special Guests: Greg WhitworthIn this episode, the JavaScript Jabber panelists discuss the effects of JavaScript on CSS with Greg Whitworth. Greg works on Microsoft EdgeHTML, specifically working on the Microsoft Layout team, is on the CSS working group, and is involved with the Houdini task force. They talk about JS engines and rendering engines, what the CSSOM is, why it is important to understand the rendering engine, and much more!In particular, we dive pretty deep on:Greg introWhat is the Houdini task force?Extensible web manifestoDOM (Document Object Model)Layout APIParser APIBabeljQueryBack to basicsJavaScript engine and rendering engineWhat is the CSSOM?Every browser has its separate JS engineBrowsers perspectiveAimee ShopTalk Podcast EpisodeWhy is it important to understand how the rendering engine is working?Making wise decisionsGive control back to browser if possibleWhen you would want to use JavaScript or CSSHard to make a hard or fast ruleCSS is more performantOverview of stepsAnd much, much more!Links:Parser APIBabeljQueryAimee ShopTalk Podcast EpisodeJavaScript@gregwhitworthGWhitworth.comGreg’s GitHub SponsorsKendo UILinodeFreshBooksPicks:AJMicrosoft SurfaceMicrosoft CursorAimeeGreg’s TalkWhat Your Conference Proposal Is Missing by Sarah MeiGregAimee ShopTalk Podcast EpisodeJake Archibald Tasks TalkSupport 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 Mai 201853min

JSJ 314: Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver LIVE at Microsoft Build

JSJ 314: Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver LIVE at Microsoft Build

Panel: Charles Max Wood Special Guests: Matt Hernandez and Amanda SilverIn this episode, the JavaScript Jabber/Adventures In Angular, panelists discuss Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver at Microsoft Build. Amanda is the director of program management at Microsoft working on Visual Studio and VS Code. Matt works on a mix between the Azure and the VS Code team, where he leads the effort to build the Azure extensions in VS code, trying to bring JavaScript developers to Azure through great experiences in VS Code. They talk about what’s new in VS Code, how the Azure extension works, what log points are, and much more!In particular, we dive pretty deep on:Amanda introMatt introWhat’s new in VS Code?VS Code coreVS Live ShareShared TerminalNow have Linux supportLive Share is now public to the world for freeWhat would you use Shared Terminal for?Are there other things coming up in VS Code?Constantly responding to requests from the communityLive Share works for any languageHow does the Azure extension work?Azure App ServiceStorage extensionAzure Cosmos DBWhat are log points?All a part of a larger plan to create a better experience for JS developersVisual debuggersIs it the same plugin to support everything on Azure?Want to target specific services that node developers will take advantage ofAnd much, much more!Links:Visual StudioVS CodeAzureLive ShareAzure Cosmos DBMicrosoft BuildAzure App ServiceAmanda’s GitHub@amandaksilverMatt’s GitHub@fiveisprimePicks:CharlesOrphan BlackShout out to VS Code teamBattle of the BooksMattThe Customer-Driven Playbook by Travis LowdermilkThe Speed of Trust by Stephen M.R. CoveyYes, And by Kelly LeonardDigital Marketing For Dummies by Ryan DeissEd Gets His Power Back KickstarterAmandaMicrosoft Quantum Development Kit for Visual Studio CodeIggy Peck, ArchitectTek by Patrick McDonnellSupport 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.

22 Mai 201850min

JSJ 313: Light Functional JavaScript with Kyle Simpson

JSJ 313: Light Functional JavaScript with Kyle Simpson

Panel: AJ ONealAimee KnightJoe Eames Special Guests: Kyle SimpsonIn this episode, the JavaScript Jabber panelists discuss light functional JavaScript with Kyle Simpson. Kyle is most well-known for writing the books You Don’t Know JS and is on the show today for his book Functional-Light JavaScript. They talk about what functional programming is, what side-effects are, and discuss the true heart behind functional programming. They also touch on the main focus of functional programming and much more!In particular, we dive pretty deep on:You Don’t Know JSFunctional-Light JavaScriptFrom the same spirit as first booksJavaScript Documents journey of learningWhat does Functional Programming mean?Functional programming is being re-awokenMany different definitionsHistory of functional programmingProgramming with functionsWhat is a function?“A collection of operations of doing some task” is what people think functions areWhat a function really isMap inputs to outputsWhat is a side-effect?Side-effects should be intentional and explicitThe heart of functional programmingRefactoringCan’t write a functional program from scratchWhat functional programming focuses onMaking more readable and reliable codePulling a time-stampDefining a side-effectAnd much, much more!Links:You Don’t Know JSFunctional-Light JavaScriptJavaScriptKyle’s GitHub@getifyPicks:AimeeWhat Does Code Readability Mean?@FunctionalKnoxHTTP 203 Podcast AJIKEAJoeBarking Up the Wrong Tree by Eric BarkerWorkshops in generalKyleGDPRThe start-up’s guide to the GDPRHatchFluent ConfSupport 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.

15 Mai 201811min

JSJ 312: Hygen with Dotan Nahum

JSJ 312: Hygen with Dotan Nahum

Panel: Charles Max WoodAimee KnightAJ ONeal Special Guests: Dotan NahumIn 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 introWhat is Hygen?Code generatorsRails in 2006Ruby on Rails 15-minute blog videoPHP and PythonCarried Rails wow moment with him into creating HygenWanted Rails generators everywhereCan you also modify files?Took the good things from Rails generatorThe fact that front-end apps have architecture is newReduxThe solution of generating codeA component is a ray of files and assetsJavaScript gives you great freedomA standardized way of doing componentsGraphQLEverything lives in the “day job” projectHow the Hygen template is formattedCan have a shell actionIs there a way to share generators in a separate package?GoAnd much, much more!Links:HygenRailsRuby on Rails 15-minute blog videoPythonReduxJavaScriptGraphQLGo@jondotDotan’s GitHubDotan’s MediumPicks:CharlesFluent ConfHot JarDevChat.tvEthereumAimeeDeep-copying in JavaScriptAJLet’s EncryptNintendo SwitchBreath of the WildDotanasdfBrew CaskSupport 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.

9 Mai 201848min

JSJ 311: Securing Express Apps with Helmet.js with Evan Hahn

JSJ 311: Securing Express Apps with Helmet.js with Evan Hahn

Panel: Charles Max Wood Special Guests: Evan HahnIn this episode, the JavaScript Jabber panelists discuss securing Express apps with Helmet.js with Evan Hahn. Evan is a developer at Airtable, which is a company that builds spreadsheet applications that are powerful enough that you can make applications with. He has also worked at Braintree, which does payment processing for companies. They talk about what Helmet.js is, when you would want to use it, and why it can help secure your Express apps. They also touch on when you wouldn’t want to use Helmet and the biggest thing that it saves you from in your code.In particular, we dive pretty deep on:Evan introJavaScript What is Helmet.js?Node and ExpressWhy would you use the approach of Middleware?Helmet is not the only solutionHttp headersCurrent maintainer of Helmet.jsnpmHas added a lot to the project, but is not the original creatorOutbound HTTP response headersHelmet doesn’t fully secure your app but it does help secure itHow does using Helmet work?Are there instances when you wouldn’t want to use Helmet?No cash middlewareWhere do you set the configuration options?Top level Helmet module12 modulesWhat is the biggest thing that Helmet saves you from?Content security policy codeAnd much, much more!Links:AirtableBraintreeJavaScriptHelmet.jsNodeExpressnpmEvan’s Website@EvanHahnEvan’s GitHubPicks:CharlesCameraZoom H6Shure SM58DevChat.tv YoutubeReact Round UpEvanClojureFortuneKantaro: The Sweet Tooth SalarymanSupport 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.

1 Mai 201840min

JSJ 310: Thwarting Insider Threats with Greg Kushto

JSJ 310: Thwarting Insider Threats with Greg Kushto

Panel: Charles Max WoodCory HouseAJ O’NealAimee Knight Special Guests: Greg KushtoIn this episode, the JavaScript Jabber panelists discuss thwarting insider threats with Greg Kushto. Greg is the vice president of sales engineering for Force 3 and has been focused on computer security for the last 25 years. They discuss what insider threats are, what the term includes, and give examples of what insider threats look like. They also touch on some overarching principles that companies can use to help prevent insider threats from occurring.In particular, we dive pretty deep on:Greg introInsider threats are a passion of hisMost computer attacks come from the inside of the companyInsider threats have changed over timeWhat does the term “insider threats” include?Using data in an irresponsible mannerWho’s fault is it?Blame the company or blame the employee?Need to understand that insider threats don’t always happen on purposeHow to prevent insider threatsVery broad termAre there some general principles to implement?Figure out what exactly you are doing and documenting itDocumentations doesn’t have to be a punishmentKnow what data you have and what you need to do to protect itHow easy it is to get hackedPractical things to keep people from clicking on curious linksThe need to change the gameFighting insider threats isn’t fun, but it is necessaryAnd much, much more!Links:Force 3Greg’s LinkedIn@Greg_KushtoGreg’s BLogPicks:CharlesHaveIBeenPwned.comPlural SightElixir podcast coming soonNG confMicroConfRubyHackMicrosoft BuildCoryPlopVS code sync pluginAimeeAwesome Proposals GitHubAJ O’NealFluffy PancakesThe Mind and the Brain by Jeffrey M. SchwartzGregStormCastSupport 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.

24 Apr 201846min

JSJ 309: WebAssembly and JavaScript with Ben Titzer

JSJ 309: WebAssembly and JavaScript with Ben Titzer

Panel: Charles Max WoodCory HouseAimee Knight Special Guests: Ben TitzerIn this episode, the JavaScript Jabber panelists discuss WebAssembly and JavaScript with Ben Titzer. Ben is a JavaScript VM engineer and is on the V8 team at Google. He was one of the co-inventors of WebAssembly and he now works on VM engineering as well as other things for WebAssembly. They talk about how WebAssembly came to be and when it would be of most benefit to you in your own code.In particular, we dive pretty deep on:Ben introJavaScriptCo-inventor of WebAssembly (Wasm)Joined V8 in 2014asm.jsBuilt a JIT compiler to make asm.js fasterTurboFanWhat is the role of JavaScript? What is the role of WebAssembly?SIMD.jsJavaScript is not a statically typed languageAdding SIMD to Wasm was easierEasy to add things to WasmWill JavaScript benefit?Using JavaScript with Wasm pros and consPros to compiling with WasmStatically typed languagesThe more statically typed you are, the more you will benefit from WasmTypeScriptIs WebAssembly headed towards being used in daily application?Rust is investing heavily in WasmWebAssembly in gamingAnd much, much more!Links:JavaScriptV8WebAssemblyasm.jsTurboFanTypeScriptRustWebAssembly GitHubBen’s GitHubPicks:CharlesReady Player One MovieDevChat.tv YouTubeAlexa Flash Briefings: Add skill for “JavaScript Rants”Corynpm Semantic Version CalculatorKent Beck TweetAimeeMDN 418 Status codeQuantity Always Trumps Quality blog postBenAmerican PoliticsSupport 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 Apr 201852min

JSJ 309: WebAssembly and JavaScript with Ben Titzer

JSJ 309: WebAssembly and JavaScript with Ben Titzer

Panel: Charles Max WoodCory HouseAimee Knight Special Guests: Ben TitzerIn this episode, the JavaScript Jabber panelists discuss WebAssembly and JavaScript with Ben Titzer. Ben is a JavaScript VM engineer and is on the V8 team at Google. He was one of the co-inventors of WebAssembly and he now works on VM engineering as well as other things for WebAssembly. They talk about how WebAssembly came to be and when it would be of most benefit to you in your own code.In particular, we dive pretty deep on:Ben introJavaScriptCo-inventor of WebAssembly (Wasm)Joined V8 in 2014asm.jsBuilt a JIT compiler to make asm.js fasterTurboFanWhat is the role of JavaScript? What is the role of WebAssembly?SIMD.jsJavaScript is not a statically typed languageAdding SIMD to Wasm was easierEasy to add things to WasmWill JavaScript benefit?Using JavaScript with Wasm pros and consPros to compiling with WasmStatically typed languagesThe more statically typed you are, the more you will benefit from WasmTypeScriptIs WebAssembly headed towards being used in daily application?Rust is investing heavily in WasmWebAssembly in gamingAnd much, much more!Links:JavaScriptV8WebAssemblyasm.jsTurboFanTypeScriptRustWebAssembly GitHubBen’s GitHubPicks:CharlesReady Player One MovieDevChat.tv YouTubeAlexa Flash Briefings: Add skill for “JavaScript Rants”Corynpm Semantic Version CalculatorKent Beck TweetAimeeMDN 418 Status codeQuantity Always Trumps Quality blog postBenAmerican PoliticsSupport 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 Apr 201852min

Populært innen Business og økonomi

stopp-verden
dine-penger-pengeradet
lydartikler-fra-aftenposten
e24-podden
rss-penger-polser-og-politikk
rss-borsmorgen-okonominyhetene
utbytte
tid-er-penger-en-podcast-med-peter-warren
pengepodden-2
okonomiamatorene
morgenkaffen-med-finansavisen
finansredaksjonen
lederpodden
pengesnakk
rss-finansforum-2
rss-markedspuls-2
livet-pa-veien-med-jan-erik-larssen
rss-impressions-2
rss-andelige-tanker-med-camillo
lederskap-nhhs-podkast-om-ledelse