Podcasts about kendo ui

Play Episode Listen Later Mar 5, 2019 37:56

Sponsors Kendo UI Sentry use the code “devchat” for $100 credit Clubhouse CacheFly Panel Joe Eames Aimee Knight Joined by special guest: Richard Feldman Episode Summary In this episode of JavaScript Jabber, Richard Feldman, primarily known for his work in Elm, the author of “Elm in Action” and Head of Technology at NoRedInk, talks about Elm 0.19 and the new features introduced in it. He explains how the development work is distributed between the Elm creator – Evan Czaplicki and the other members of the community and discusses the challenges on the way to Elm 1.0. Richard also shares some educational materials for listeners interested in learning Elm and gives details on Elm conferences around the world touching on the topic of having diversity among the speakers. He finally discusses some exciting things about Elm which would encourage developers to work with it. Links Elm in Action Frontend Masters – Introduction to Elm Frontend Masters – Advanced Elm Small Assets without the Headache Elm Guide ElmBridge San Francisco Renee Balmert Picks Aimee Knight: Most lives are lived by default Joe Eames: Thinkster Richard Feldman: Framework Summit 2018 – Keynote speech Nix Package Manager A Philosophy of Software Design

head technology action philosophy panel clubhouse keynote headaches elm sentry software design cachefly richard feldman noredink frontend masters aimee knight javascript jabber kendo ui joe eames evan czaplicki thinkster framework summit

JSJ 354: Elm with Richard Feldman

Play Episode Listen Later Mar 5, 2019 37:56

Sponsors Kendo UI Sentry use the code “devchat” for $100 credit Clubhouse CacheFly Panel Joe Eames Aimee Knight Joined by special guest: Richard Feldman Episode Summary In this episode of JavaScript Jabber, Richard Feldman, primarily known for his work in Elm, the author of “Elm in Action” and Head of Technology at NoRedInk, talks about Elm 0.19 and the new features introduced in it. He explains how the development work is distributed between the Elm creator – Evan Czaplicki and the other members of the community and discusses the challenges on the way to Elm 1.0. Richard also shares some educational materials for listeners interested in learning Elm and gives details on Elm conferences around the world touching on the topic of having diversity among the speakers. He finally discusses some exciting things about Elm which would encourage developers to work with it. Links Elm in Action Frontend Masters – Introduction to Elm Frontend Masters – Advanced Elm Small Assets without the Headache Elm Guide ElmBridge San Francisco Renee Balmert Picks Aimee Knight: Most lives are lived by default Joe Eames: Thinkster Richard Feldman: Framework Summit 2018 – Keynote speech Nix Package Manager A Philosophy of Software Design

head technology action philosophy panel clubhouse keynote headaches elm sentry software design cachefly richard feldman noredink frontend masters aimee knight javascript jabber kendo ui joe eames evan czaplicki thinkster framework summit

VoV 047: Games & Other Novel Uses for Vue with Kevin Drum

Play Episode Listen Later Feb 5, 2019 52:54

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit TripleByte Panel: Chris Fritz Divya Sasidharan Erik Hatchett Charles Max Wood Special Guest: Kevin Drum Notes: This episode features special guest Kevin Drum from Virginia. Kevin is a remote developer for Asteris, a company supplying tech to veterinarians based out of Colorado. Kevin works daily on a Vue app called Keystone Omni which provides imaging solutions for veterinarians, but was invited on the show because he made a blackjack game with Vue. The panel discusses his inspiration for making a game with Vue, since Vue is most often used to manage data. Kevin details the technologies he used to create his game, including GreenSock and the influence of Vue X on the design of his app. He discusses some of the bugs he encountered while creating his game. Kevin talks about designing the interface with Figma and the caution that should be taken when adding sound effects to a game. He discusses his decision to use Canvas and WebGL, as well as other technologies like Vue Babylon JS. The panelists talk about shaders, an algorithm that will manipulate shapes, and the difficulties with using them. They talk about how to get started making your own game. Kevin advises listeners to first focus on the logic of the game and then on the aesthetics, encouraging a “make it work first, then make it pretty later” approach. They also encourage listeners to play around with Vue by making a demo app first to practice changing all the different properties of the elements. The panelists talk about other uses for Vue in games and if there are benefits to writing a game loop outside of Vue. Chris highlights the #vuenicorn contest that was hosted on twitter. Terms: Canvas Dom elements SVG CSS GreenSock webGL Node VueX Figma Tone JS Vue Babylon JS Unity Native Electron Cordova Capacitor Shaders Phaser Web audio API Picks: Chris: CrossCode Vue Conf US Workshops Erik: Let's talk about an unnecessary but popular Vue plugin article Charles: McKirdy Trained Running Coaches Garmin Foreunner Watch Kevin: Refactoring UI Game Programming Patterns

games colorado unity web panel terms dom native api canvas css node figma vue cordova sentry electron beg svg capacitors phaser crosscode webgl charles max wood shaders triplebyte kendo ui refactoring ui chris fritz divya sasidharan greensock kevin drum nativescript nativescript

RRU 047: Expo with Charlie Cheever

Play Episode Listen Later Feb 5, 2019 63:10

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit TripleByte $1000 signing bonus Cachefly Panel: Nader Dabit Justin Bennett Charles Max Wood Special Guest: Charlie Cheever Notes: This episode of React Round Up has the panelists talking to Charlie Cheever, a former Facebook employee, who currently works on Expo. The panel discusses Charlies article called “Should we be using React Native?”, Airbnb sunsetting their React Native app, and the nature of the Expo app. Charlie describes Expo as the easiest way to do React Native using just JavaScript, and making it as easy and powerful as possible. Expo works kind of like a web browser for JavaScript, and is available on iOS, Android, and and Google app stores. Expo CLI has replaced Create React Native CLI because Expo is more user friendly. Many features are already included in Expo, including OTA updates, dealing with fonts, video player, Facebook ad and Google ads, barcode scanner, Native maps, and much more. To get started on your computer, go to snack.expo.io or download the Expo app on your phone. The panelists chat about the success of Charlie’s company and how he has attracted so many great programmers to his company. Charlie gives a history of how Expo got started. Charlie gives advice on how to start a business around a free tool, and the goal of Expo to make every service available on the app before focusing on making money. The panel discusses sustainability in the software world, as making people pay for things can drive them to write their own stuff. They talk about the benefits of using Expo and its ability to cross platforms, and enterprise companies such as Youtube and Instagram shifting over to using React. Charlie attributes this shift to two things; the increase in software developer salaries driving down the number of available software engineers, which makes it difficult for smaller companies to hire engineers, thus pushing them to use things like React and Expo to make up for it. Last, the panelists talk about the possibility that the world is moving towards a future characterized by a “write once, run everywhere” and more uniform experiences across operating systems. Terms: React Native Expo Expo CLI VS Code Emacs Vim Xamarin Titanium Native Script AWS Picks: Nader: Video series on Egghead On Grand Strategy Justin: rePNG Dark Reader Charles: Pomodoro method Kanbonflow John Somnez video Charlie: React navigation React Native Gesture Handler React Native Reanimated Wiliam Candelon “Can It Be Done in React Native” videos

google video android airbnb panel ios terms native react expo aws javascript ota pomodoro nader titanium sentry charlies vim vs code eggheads react native xamarin emacs cheever cachefly nader dabit charles max wood triplebyte justin bennett kendo ui react round up on grand strategy nativescript nativescript

VoV 047: Games & Other Novel Uses for Vue with Kevin Drum

Play Episode Listen Later Feb 5, 2019 52:54

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit TripleByte Panel: Chris Fritz Divya Sasidharan Erik Hatchett Charles Max Wood Special Guest: Kevin Drum Notes: This episode features special guest Kevin Drum from Virginia. Kevin is a remote developer for Asteris, a company supplying tech to veterinarians based out of Colorado. Kevin works daily on a Vue app called Keystone Omni which provides imaging solutions for veterinarians, but was invited on the show because he made a blackjack game with Vue. The panel discusses his inspiration for making a game with Vue, since Vue is most often used to manage data. Kevin details the technologies he used to create his game, including GreenSock and the influence of Vue X on the design of his app. He discusses some of the bugs he encountered while creating his game. Kevin talks about designing the interface with Figma and the caution that should be taken when adding sound effects to a game. He discusses his decision to use Canvas and WebGL, as well as other technologies like Vue Babylon JS. The panelists talk about shaders, an algorithm that will manipulate shapes, and the difficulties with using them. They talk about how to get started making your own game. Kevin advises listeners to first focus on the logic of the game and then on the aesthetics, encouraging a “make it work first, then make it pretty later” approach. They also encourage listeners to play around with Vue by making a demo app first to practice changing all the different properties of the elements. The panelists talk about other uses for Vue in games and if there are benefits to writing a game loop outside of Vue. Chris highlights the #vuenicorn contest that was hosted on twitter. Terms: Canvas Dom elements SVG CSS GreenSock webGL Node VueX Figma Tone JS Vue Babylon JS Unity Native Electron Cordova Capacitor Shaders Phaser Web audio API Picks: Chris: CrossCode Vue Conf US Workshops Erik: Let's talk about an unnecessary but popular Vue plugin article Charles: McKirdy Trained Running Coaches Garmin Foreunner Watch Kevin: Refactoring UI Game Programming Patterns

games colorado unity web panel terms dom native api canvas css node figma vue cordova sentry electron beg svg capacitors phaser crosscode webgl charles max wood shaders triplebyte kendo ui refactoring ui chris fritz divya sasidharan greensock kevin drum nativescript nativescript

RRU 047: Expo with Charlie Cheever

Play Episode Listen Later Feb 5, 2019 63:10

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit TripleByte $1000 signing bonus Cachefly Panel: Nader Dabit Justin Bennett Charles Max Wood Special Guest: Charlie Cheever Notes: This episode of React Round Up has the panelists talking to Charlie Cheever, a former Facebook employee, who currently works on Expo. The panel discusses Charlies article called “Should we be using React Native?”, Airbnb sunsetting their React Native app, and the nature of the Expo app. Charlie describes Expo as the easiest way to do React Native using just JavaScript, and making it as easy and powerful as possible. Expo works kind of like a web browser for JavaScript, and is available on iOS, Android, and and Google app stores. Expo CLI has replaced Create React Native CLI because Expo is more user friendly. Many features are already included in Expo, including OTA updates, dealing with fonts, video player, Facebook ad and Google ads, barcode scanner, Native maps, and much more. To get started on your computer, go to snack.expo.io or download the Expo app on your phone. The panelists chat about the success of Charlie’s company and how he has attracted so many great programmers to his company. Charlie gives a history of how Expo got started. Charlie gives advice on how to start a business around a free tool, and the goal of Expo to make every service available on the app before focusing on making money. The panel discusses sustainability in the software world, as making people pay for things can drive them to write their own stuff. They talk about the benefits of using Expo and its ability to cross platforms, and enterprise companies such as Youtube and Instagram shifting over to using React. Charlie attributes this shift to two things; the increase in software developer salaries driving down the number of available software engineers, which makes it difficult for smaller companies to hire engineers, thus pushing them to use things like React and Expo to make up for it. Last, the panelists talk about the possibility that the world is moving towards a future characterized by a “write once, run everywhere” and more uniform experiences across operating systems. Terms: React Native Expo Expo CLI VS Code Emacs Vim Xamarin Titanium Native Script AWS Picks: Nader: Video series on Egghead On Grand Strategy Justin: rePNG Dark Reader Charles: Pomodoro method Kanbonflow John Somnez video Charlie: React navigation React Native Gesture Handler React Native Reanimated Wiliam Candelon “Can It Be Done in React Native” videos

google video android airbnb panel ios terms native react expo aws javascript ota pomodoro nader titanium sentry charlies vim vs code eggheads react native xamarin emacs cheever cachefly nader dabit charles max wood triplebyte justin bennett kendo ui react round up on grand strategy nativescript nativescript

JSJ 349: Agile Development - The Technical Side with James Shore

Play Episode Listen Later Jan 30, 2019 59:46

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guest: James Shore Episode Summary James Shore is a developer who specializing in extreme programming, an Agile method. He also used to host a screencast called Let’s Code Test-Driven JavaScript. They begin by discussing the core of Agile development, which James believes is being responsive to customers and business partners in a way that’s sustainable and humane for the programmers involved. It prioritizes individuals and interactions over processes and tools. More can be found in The Agile Manifesto. James delves into the historical context of the immersion of Agile and how things have changed from the 90’s. Now, the name Agile is everywhere, but the ideals of agile are not as common. There is a tendency to either take Agile buzzwords and apply them to the way it was done long ago, or it’s absolute chaos. James talks about ways to implement Agile in the workplace. He believes that the best way to learn Agile is work with someone who knows Agile, or read a book on it and then apply it. James recommends his book The Art of Agile Development: Pragmatic Guide to Agile Software Development for people who want to started with Agile development. The panelists talk about where people often get stuck with implementing Agile. The hosts talk about their own processes in their company. They discuss how people involved in the early days of Agile are disappointed in how commercial it has become.They agree that what’s really the most important is the results. If you can respond to a request to change direction in less than two weeks and you don’t have to spend months and months preparing something, and you do that in a way where the people on the team feel like their contributing, then you’re doing Agile. James thinks that the true genius of Agile is in the way the actual work is done rather than in the way your organize the work. Links Agile Scrum Waterfall Feature Driven Development Extreme Programming (XP) Jira Bamboo Confluence Atlassian stack Cowboy Mock objects Grows Method by Andy Hunt Picks AJ O’Neal: Origin by Dan Brown Searching Aimee Knight: Hacker News Interview Questions Thread. Joe Eames: The Ballad of Buster Scruggs on Netflix Charles Max Wood: Getting up early John Sonmez Kanbanflow video Drip James Shore: Lost in Space on Netflix Star Citizen PC game Jame’s Agile book online

VoV 046: Component Composition at Kong with Darren Jennings

Play Episode Listen Later Jan 29, 2019 71:08

Sponsors KendoUI Sentry use the code "devchat" for $100 credit TripleByte CacheFly Panel Chris Fritz Divya Sasidharan Joe Eames Charles Max Wood Joined by Special Guest: Darren Jennings Summary Darren Jennings talks about his open source component vue-autosuggest and his experience open sourcing it. He talks about support, use cases, and feature implementation. The panel shares support request stories. Darren gives tips for open sourcing and making components more reusable. He shares his favorite tools for composing components. He explains the benefits he has seen open sourcing this component. Links https://openresty.org/en/ https://konghq.com/ https://github.com/Educents/vue-autosuggest https://vuejsdevelopers.com/2018/01/15/vue-js-render-props https://medium.com/@darrenjennings/open-sourcing-your-first-vue-component-5ef015e1f66c https://twitter.com/darrenjennings https://www.facebook.com/ViewsonVue https://twitter.com/viewsonvue Picks Charles Max Wood: http://entreprogrammers.com/ The Pomodoro Technique: The Acclaimed Time-Management System That Has Transformed How We Work https://kanbanflow.com/ https://www.11ty.io/ https://www.netlify.com/ Darren Jennings: Xstate library Hollow Knight - Nintendo Switch vue-autosuggest Chris Fritz http://www.matthewbrowngames.com/hexcellsinfinite.html Be vulnerable with people in your life. The Power of Vulnerability: Teachings of Authenticity, Connection, and Courage Divya Sasidharan: https://24ways.org/ https://calendar.perfplanet.com http://shortdiv.com/ Joe Eames: Framework Summit ng-conf minified Give

power courage authenticity panel kong jennings composition component sentry cachefly charles max wood triplebyte xstate vulnerability teachings kendo ui chris fritz joe eames divya sasidharan framework summit lk12i5e0hay

RRU 046: GraphQL vs REST APIs with Max Desiatov

Play Episode Listen Later Jan 29, 2019 69:28

Sponsors KendoUI Sentry use the code “devchat” for $100 credit TripleByte Cachefly Panel Lucas Reis Justin Bennett Charles Max Wood Joined by Special Guest: Max Desiatov Summary Max Desiatov shares his experience transitioning from REST to GraphQL. The panel discusses Max’s migration strategy and other strategies. REST and GraphQL are compared, the problems with both are discussed. The panel shares their favorite things about GraphQL including workflow and data modeling. The solutions for GraphQL problems are discussed and the things the panel would like to see are mentioned. Max Desiatov and Justin Bennett share the different tools they use including Apollo and Graphiql. Charles Max Wood steers the conversation to the adoption of GraphQL by companies. Links https://sailsjs.com/ https://graphql.org https://spring.io/understanding/HATEOAS https://www.graphile.org/postgraphile/ https://www.apollographql.com/docs/react/ https://github.com/expo/apollo-codegen https://github.com/graphql/graphiql https://www.apollographql.com/docs/graphql-tools/schema-stitching.html https://www.apollographql.com/docs/react/essentials/local-state.html https://desiatov.com/why-graphql/ https://desiatov.com/ https://twitter.com/maxdesiatov https://github.com/maxdesiatov Picks Justin Bennett https://renovatebot.com/ The Wheel of Time by Robert Jordan and Brandon Sanderson Charles Max Wood https://www.11ty.io/ https://devchat.tv/ruby-rogues/rr-383-rbspy-a-newish-ruby-profiler-with-julia-evans/ Max Desiatov https://nadiaeghbal.com https://jvns.ca/blog/2018/09/18/build-impossible-programs/

time panel wheel apollo brandon sanderson sentry graphql robert jordan rest apis cachefly charles max wood triplebyte justin bennett kendo ui lucas reis

JSJ 349: Agile Development - The Technical Side with James Shore

Play Episode Listen Later Jan 29, 2019 59:46

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guest: James Shore Episode Summary James Shore is a developer who specializing in extreme programming, an Agile method. He also used to host a screencast called Let’s Code Test-Driven JavaScript. They begin by discussing the core of Agile development, which James believes is being responsive to customers and business partners in a way that’s sustainable and humane for the programmers involved. It prioritizes individuals and interactions over processes and tools. More can be found in The Agile Manifesto. James delves into the historical context of the immersion of Agile and how things have changed from the 90’s. Now, the name Agile is everywhere, but the ideals of agile are not as common. There is a tendency to either take Agile buzzwords and apply them to the way it was done long ago, or it’s absolute chaos. James talks about ways to implement Agile in the workplace. He believes that the best way to learn Agile is work with someone who knows Agile, or read a book on it and then apply it. James recommends his book The Art of Agile Development: Pragmatic Guide to Agile Software Development for people who want to started with Agile development. The panelists talk about where people often get stuck with implementing Agile. The hosts talk about their own processes in their company. They discuss how people involved in the early days of Agile are disappointed in how commercial it has become.They agree that what’s really the most important is the results. If you can respond to a request to change direction in less than two weeks and you don’t have to spend months and months preparing something, and you do that in a way where the people on the team feel like their contributing, then you’re doing Agile. James thinks that the true genius of Agile is in the way the actual work is done rather than in the way your organize the work. Links Agile Scrum Waterfall Feature Driven Development Extreme Programming (XP) Jira Bamboo Confluence Atlassian stack Cowboy Mock objects Grows Method by Andy Hunt Picks AJ O’Neal: Origin by Dan Brown Searching Aimee Knight: Hacker News Interview Questions Thread. Joe Eames: The Ballad of Buster Scruggs on Netflix Charles Max Wood: Getting up early John Sonmez Kanbanflow video Drip James Shore: Lost in Space on Netflix Star Citizen PC game Jame’s Agile book online

JSJ 349: Agile Development - The Technical Side with James Shore

Play Episode Listen Later Jan 29, 2019 59:46

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guest: James Shore Episode Summary James Shore is a developer who specializing in extreme programming, an Agile method. He also used to host a screencast called Let’s Code Test-Driven JavaScript. They begin by discussing the core of Agile development, which James believes is being responsive to customers and business partners in a way that’s sustainable and humane for the programmers involved. It prioritizes individuals and interactions over processes and tools. More can be found in The Agile Manifesto. James delves into the historical context of the immersion of Agile and how things have changed from the 90’s. Now, the name Agile is everywhere, but the ideals of agile are not as common. There is a tendency to either take Agile buzzwords and apply them to the way it was done long ago, or it’s absolute chaos. James talks about ways to implement Agile in the workplace. He believes that the best way to learn Agile is work with someone who knows Agile, or read a book on it and then apply it. James recommends his book The Art of Agile Development: Pragmatic Guide to Agile Software Development for people who want to started with Agile development. The panelists talk about where people often get stuck with implementing Agile. The hosts talk about their own processes in their company. They discuss how people involved in the early days of Agile are disappointed in how commercial it has become.They agree that what’s really the most important is the results. If you can respond to a request to change direction in less than two weeks and you don’t have to spend months and months preparing something, and you do that in a way where the people on the team feel like their contributing, then you’re doing Agile. James thinks that the true genius of Agile is in the way the actual work is done rather than in the way your organize the work. Links Agile Scrum Waterfall Feature Driven Development Extreme Programming (XP) Jira Bamboo Confluence Atlassian stack Cowboy Mock objects Grows Method by Andy Hunt Picks AJ O’Neal: Origin by Dan Brown Searching Aimee Knight: Hacker News Interview Questions Thread. Joe Eames: The Ballad of Buster Scruggs on Netflix Charles Max Wood: Getting up early John Sonmez Kanbanflow video Drip James Shore: Lost in Space on Netflix Star Citizen PC game Jame’s Agile book online

RRU 046: GraphQL vs REST APIs with Max Desiatov

Play Episode Listen Later Jan 29, 2019 69:28

Sponsors KendoUI Sentry use the code “devchat” for $100 credit TripleByte Cachefly Panel Lucas Reis Justin Bennett Charles Max Wood Joined by Special Guest: Max Desiatov Summary Max Desiatov shares his experience transitioning from REST to GraphQL. The panel discusses Max’s migration strategy and other strategies. REST and GraphQL are compared, the problems with both are discussed. The panel shares their favorite things about GraphQL including workflow and data modeling. The solutions for GraphQL problems are discussed and the things the panel would like to see are mentioned. Max Desiatov and Justin Bennett share the different tools they use including Apollo and Graphiql. Charles Max Wood steers the conversation to the adoption of GraphQL by companies. Links https://sailsjs.com/ https://graphql.org https://spring.io/understanding/HATEOAS https://www.graphile.org/postgraphile/ https://www.apollographql.com/docs/react/ https://github.com/expo/apollo-codegen https://github.com/graphql/graphiql https://www.apollographql.com/docs/graphql-tools/schema-stitching.html https://www.apollographql.com/docs/react/essentials/local-state.html https://desiatov.com/why-graphql/ https://desiatov.com/ https://twitter.com/maxdesiatov https://github.com/maxdesiatov Picks Justin Bennett https://renovatebot.com/ The Wheel of Time by Robert Jordan and Brandon Sanderson Charles Max Wood https://www.11ty.io/ https://devchat.tv/ruby-rogues/rr-383-rbspy-a-newish-ruby-profiler-with-julia-evans/ Max Desiatov https://nadiaeghbal.com https://jvns.ca/blog/2018/09/18/build-impossible-programs/

time panel wheel apollo brandon sanderson sentry graphql robert jordan rest apis cachefly charles max wood triplebyte justin bennett kendo ui lucas reis

VoV 046: Component Composition at Kong with Darren Jennings

Play Episode Listen Later Jan 29, 2019 71:08

Sponsors KendoUI Sentry use the code "devchat" for $100 credit TripleByte CacheFly Panel Chris Fritz Divya Sasidharan Joe Eames Charles Max Wood Joined by Special Guest: Darren Jennings Summary Darren Jennings talks about his open source component vue-autosuggest and his experience open sourcing it. He talks about support, use cases, and feature implementation. The panel shares support request stories. Darren gives tips for open sourcing and making components more reusable. He shares his favorite tools for composing components. He explains the benefits he has seen open sourcing this component. Links https://openresty.org/en/ https://konghq.com/ https://github.com/Educents/vue-autosuggest https://vuejsdevelopers.com/2018/01/15/vue-js-render-props https://medium.com/@darrenjennings/open-sourcing-your-first-vue-component-5ef015e1f66c https://twitter.com/darrenjennings https://www.facebook.com/ViewsonVue https://twitter.com/viewsonvue Picks Charles Max Wood: http://entreprogrammers.com/ The Pomodoro Technique: The Acclaimed Time-Management System That Has Transformed How We Work https://kanbanflow.com/ https://www.11ty.io/ https://www.netlify.com/ Darren Jennings: Xstate library Hollow Knight - Nintendo Switch vue-autosuggest Chris Fritz http://www.matthewbrowngames.com/hexcellsinfinite.html Be vulnerable with people in your life. The Power of Vulnerability: Teachings of Authenticity, Connection, and Courage Divya Sasidharan: https://24ways.org/ https://calendar.perfplanet.com http://shortdiv.com/ Joe Eames: Framework Summit ng-conf minified Give

power courage authenticity panel kong jennings composition component sentry cachefly charles max wood triplebyte xstate vulnerability teachings kendo ui chris fritz joe eames divya sasidharan framework summit lk12i5e0hay

VoV 045: Comparing the React and Vue Ecosystems with a Real-World SPA with John Datserakis

Play Episode Listen Later Jan 23, 2019 76:41

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit TripleByte Panel: Divya Sasidharan Erik Hanchett Chris Fritz Joe Eames John Papa Charles Max Wood Special Guest: John Datserakis Episode Summary In this episode of Views on Vue, the panelists talk to John Datserakis, a full stack developer from North Shore Massachusetts. John has been programming for 9 years and works for Promosis, Inc. a company that develops and designs sweepstakes programs and other marketing tools. After leaving jQuery, John wrote a detailed tutorial comparing Vue and React. He felt that there weren’t enough tutorials available that show the issues developers face while coding in real time. With this tutorial he wanted to go through all the challenges a developer can face while learning a new framework from scratch. Comparing his favorite and least favorite parts using React, he mentions he didn’t “fall in love with it” enough to leave Vue. John then compares his experiences with Create React App and Vue CLI and talks about his most recent project, Best Meta which helps pick the most popular items on Amazon. John also talks briefly about his experiences using Vuex and Redux. Writing the detailed comparison tutorial helped John sharpen his JavaScript skills but he reveals that, at the end of the day, he will use Vue for his next project. Links Vue.js React.js John's GitHub John's Twitter John's LinkedIn Promosis, Inc. https://webpack.js.org/ https://angular.io/cli/update https://cli.vuejs.org/ https://redux.js.org/ https://www.facebook.com/ViewsonVue/ https://twitter.com/viewsonvue John's Recent Project: Best Meta John Datserakis' Article - Comparing Vue and React John Datserakis’ open-source projects on GitHub that pertain to the article: koa-vue-notes-api koa-vue-notes-web koa-react-notes-web John Datserakis' Other Recent GitHub Projects: vue-simple-context-menu vue-cookie-accept-decline vue-programmatic-invisible-google-recaptcha Picks John Papa: A book by Chris Noring on React Chris Noring's Twitter Divya Sasidharan: Framework Summit Sarah Drasner’s Workshop Design for Developers Ghost Erik Hanchett: AWS Amplify Chris Fritz: Google Fi Referral Code Ball Lightning by Cixin Liu FrontendMasters Joe Eames: ng-conf Minified – YouTube Framework Summit John Papa - AngularConnect Charles Max Wood: Eleventy Nunjucks John Datserakis: John's Recent Project: Best Meta Netlify Anthony Gore's Website

amazon ghosts writing fall in love panel views comparing developers react real world redux github javascript ecosystems vue sentry jquery netlify cixin liu eleventy ball lightning aws amplify charles max wood john papa triplebyte sarah drasner create react app kendo ui vue cli chris fritz joe eames divya sasidharan framework summit

RRU 045: React Hooks with Dave Ceddia

Play Episode Listen Later Jan 23, 2019 54:53

Sponsors KendoUI Sentry use the code “devchat” for $100 credit TripleByte Cachefly Panel Charles Max Wood Lucas Reis Justin Bennett Joined by Special Guest: Dave Ceddia Summary Dave Ceddia introduces hooks and what they let you do. The panel discusses how hooks work and how they will clean up the code. Dave explains what react does behind the scenes when hooks are being used. Hooks are simple to use but hard to explain, so the panel asks Dave how he would teach hooks. Dave explains there is a learning hump and shares what trips most developers up. The panel considers the switch from life cycles to effect and the mindset shift it requires. The difficulties of hooks are explored, such as there are now three ways to share functionality in react components. Dave shares the advantages of using array destructing instead of object destructing. The panel considers how hooks change the react framework and whether it is worth going back and refactoring everything or to refactor as you go. Different migration paths are discussed and the panel gives advice for different company types and sizes. Jokingly the panel contemplates the hype surrounding hooks and suspense. Links https://www.youtube.com/watch?v=Z2DU0qLfPIY&feature=youtu.be&t=2445 https://reactjs.org/docs/hooks-faq.html#should-i-use-hooks-classes-or-a-mix-of-both https://english.stackexchange.com/questions/12980/how-to-pronounce-tuple https://reactjs.org/blog/2018/11/27/react-16-roadmap.html https://reactjs.org/docs/hooks-intro.html https://daveceddia.com/tags/#hooks https://youtu.be/CpPCJigsPNY https://daveceddia.com/ https://twitter.com/dceddia Picks Charles Max Wood mastermindhunt.com/devchat https://devchat.tv/get-a-coder-job/ Lucas Reis https://xstate.js.org/docs/ https://github.com/carloslfu/use-machine Justin Bennett https://github.com/zeit/ncc https://parceljs.org/ https://bcrikko.github.io/NES.css/ Dave Ceddia https://codesandbox.io/docs/live https://jamesclear.com/atomic-habits

panel nes hooks sentry cachefly jokingly react hooks charles max wood triplebyte justin bennett kendo ui lucas reis

VoV 045: Comparing the React and Vue Ecosystems with a Real-World SPA with John Datserakis

Play Episode Listen Later Jan 23, 2019 76:41

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit TripleByte Panel: Divya Sasidharan Erik Hanchett Chris Fritz Joe Eames John Papa Charles Max Wood Special Guest: John Datserakis Episode Summary In this episode of Views on Vue, the panelists talk to John Datserakis, a full stack developer from North Shore Massachusetts. John has been programming for 9 years and works for Promosis, Inc. a company that develops and designs sweepstakes programs and other marketing tools. After leaving jQuery, John wrote a detailed tutorial comparing Vue and React. He felt that there weren’t enough tutorials available that show the issues developers face while coding in real time. With this tutorial he wanted to go through all the challenges a developer can face while learning a new framework from scratch. Comparing his favorite and least favorite parts using React, he mentions he didn’t “fall in love with it” enough to leave Vue. John then compares his experiences with Create React App and Vue CLI and talks about his most recent project, Best Meta which helps pick the most popular items on Amazon. John also talks briefly about his experiences using Vuex and Redux. Writing the detailed comparison tutorial helped John sharpen his JavaScript skills but he reveals that, at the end of the day, he will use Vue for his next project. Links Vue.js React.js John's GitHub John's Twitter John's LinkedIn Promosis, Inc. https://webpack.js.org/ https://angular.io/cli/update https://cli.vuejs.org/ https://redux.js.org/ https://www.facebook.com/ViewsonVue/ https://twitter.com/viewsonvue John's Recent Project: Best Meta John Datserakis' Article - Comparing Vue and React John Datserakis’ open-source projects on GitHub that pertain to the article: koa-vue-notes-api koa-vue-notes-web koa-react-notes-web John Datserakis' Other Recent GitHub Projects: vue-simple-context-menu vue-cookie-accept-decline vue-programmatic-invisible-google-recaptcha Picks John Papa: A book by Chris Noring on React Chris Noring's Twitter Divya Sasidharan: Framework Summit Sarah Drasner’s Workshop Design for Developers Ghost Erik Hanchett: AWS Amplify Chris Fritz: Google Fi Referral Code Ball Lightning by Cixin Liu FrontendMasters Joe Eames: ng-conf Minified – YouTube Framework Summit John Papa - AngularConnect Charles Max Wood: Eleventy Nunjucks John Datserakis: John's Recent Project: Best Meta Netlify Anthony Gore's Website

amazon ghosts writing fall in love panel views comparing developers react real world redux github javascript ecosystems vue sentry jquery netlify cixin liu eleventy ball lightning aws amplify charles max wood john papa triplebyte sarah drasner create react app kendo ui vue cli chris fritz joe eames divya sasidharan framework summit

RRU 045: React Hooks with Dave Ceddia

Play Episode Listen Later Jan 23, 2019 54:53

Sponsors KendoUI Sentry use the code “devchat” for $100 credit TripleByte Cachefly Panel Charles Max Wood Lucas Reis Justin Bennett Joined by Special Guest: Dave Ceddia Summary Dave Ceddia introduces hooks and what they let you do. The panel discusses how hooks work and how they will clean up the code. Dave explains what react does behind the scenes when hooks are being used. Hooks are simple to use but hard to explain, so the panel asks Dave how he would teach hooks. Dave explains there is a learning hump and shares what trips most developers up. The panel considers the switch from life cycles to effect and the mindset shift it requires. The difficulties of hooks are explored, such as there are now three ways to share functionality in react components. Dave shares the advantages of using array destructing instead of object destructing. The panel considers how hooks change the react framework and whether it is worth going back and refactoring everything or to refactor as you go. Different migration paths are discussed and the panel gives advice for different company types and sizes. Jokingly the panel contemplates the hype surrounding hooks and suspense. Links https://www.youtube.com/watch?v=Z2DU0qLfPIY&feature=youtu.be&t=2445 https://reactjs.org/docs/hooks-faq.html#should-i-use-hooks-classes-or-a-mix-of-both https://english.stackexchange.com/questions/12980/how-to-pronounce-tuple https://reactjs.org/blog/2018/11/27/react-16-roadmap.html https://reactjs.org/docs/hooks-intro.html https://daveceddia.com/tags/#hooks https://youtu.be/CpPCJigsPNY https://daveceddia.com/ https://twitter.com/dceddia Picks Charles Max Wood mastermindhunt.com/devchat https://devchat.tv/get-a-coder-job/ Lucas Reis https://xstate.js.org/docs/ https://github.com/carloslfu/use-machine Justin Bennett https://github.com/zeit/ncc https://parceljs.org/ https://bcrikko.github.io/NES.css/ Dave Ceddia https://codesandbox.io/docs/live https://jamesclear.com/atomic-habits

panel nes hooks sentry cachefly jokingly react hooks charles max wood triplebyte justin bennett kendo ui lucas reis

JSJ 348: EnactJS with Ryan Duffy

Play Episode Listen Later Jan 22, 2019 44:08

Sponsors KendoUI Sentry use the code "devchat" for $100 credit Clubhouse CacheFly Panel Aimee Knight Aaron Frost Chris Ferdinandi Joe Eames Special Guest: Ryan Duffy In this episode of JavaScript Jabber, the panelists talk with Ryan Duffy who works on the EnactJS framework at LG Electronics. Ryan explains the framework in depth and answers all the questions about its design and implementation from the panelists and discusses some challenges faced along the way. Check it out! Show Notes: 00:28 – Advertisement - KendoUI 1:08 - Ryan introduces himself and explains a bit about the EnactJS framework. While giving some background, he says that it is the 3rd generation of web frameworks that supports apps on webOS and they started building Enact on top of React about two years ago. 2:00 - Aimee asks what exactly does webOS mean. Ryan answers that webOS was created by Palm for phones and related devices and it has several instances of chromium running on device with some service layer stuff. 2:36 - Aaron mentions that webOS was big when other operating systems were still coming up, and Ryan agrees saying that it didn’t get the adoption needed to make it successful later. 3:00 - Ryan says that he always loved building apps for webOS phones given the flexibility and ease coming from a web development background. 3:53 - Aaron asks on which other applications is webOS running other than TV. Ryan answers that TV is one of the major consumptions, and it also runs on certain robots such as the concierge ones, watches to some extent and a lot of projects internally, not yet released in the market. 4:50 - Aaron asks if the Enact framework is big internally at LG. Ryan replies that it is the primary framework used for apps running on webOS. 5:03 - Aaron enquires about the nature of adoption of Enact for third party or non-LG people, to which Ryan states that Enact remains the standard framework for people who are building apps. 5:32 - Joe joins in the conversation. 6:25 - Aaron remarks that given that webOS is used in latest robots, televisions, watches and other such apps, it sounds like they are heavily investing into it. Ryan affirms by saying that the webOS journey goes from Palm phones to HP tablets to finally coming to LG. He goes on to explain their team structure, stating that there are two major teams in play right now - the R&D team is in the US and the implementation team is in Korea. 8:00 - Aaron asks about the role their team plays in the app development. Ryan replies that his team is the stack team that forms the foundation for the apps and they take decisions on what the components should look like and similar tasks. The app teams based in Korea decide their menu based on those decisions. 8:35 - Aaron asks what exactly is meant by the Blink team. Ryan answers that the it’s the team that works with an LG customized version of chromium. 9:10 – Aaron then asks about his individual role in the team. Ryan says that he is one of the managers of the stack team and he’s been on the team for little more than 4 years. 9:30 - Aaron asks about the evolution of the framework over time. Ryan describes the historical background by saying that in the initial Enyo design the team built, was component based, and every tool needed to build single page apps had to be developed from scratch. He says that they felt the need to move on to an improved framework as they wanted to take advantage of the robust ecosystem that existed, so they ported component libraries of Enyo using the React toolset to form Enact. 11:43 - Aaron asks if Enyo then ceased to exist to which Ryan states that it is still around to some extent. 12:20 - Aaron asks if the team has something like “create Enact app” to create a new app internally, like React. Ryan mentions that Jason - a tooling and automation expert from their team has built a feature called V8 snapshot - which loads JavaScript into memory and takes a snapshot - can in turn be loaded by the TV to launch the app in order to achieve a faster load time. He says that their long-term goal is to increase compatibility with the ecosystem. 14:40 - Aaron asks if he can use the React CLI to create something for TV as a third-party developer. Ryan elaborates that CLI can be used to build, compile and bundle apps and there is another tool- SDK to bundle it for delivery to the TV. The app is tested fully in chrome, bundled and deployed to the TV. 15:25 - Aaron asks if choosing React was a natural decision for the team. Ryan explains that they researched on some component-based frameworks that were available at that time and found that React was the best choice. 17:30 - Aimee asks the reason for open sourcing the framework. Ryan mentions that Enyo always has been open source. He also remarks that the team does not get a lot of input from the community and would like to get more information about what’s working and what’s not and how they can contribute back. 19:40 - Aaron asks about the kind of apps can be built by using Enact except for TV. Ryan says that any kind can be built but the hesitation is that the UI library is specially designed for TV, so they may look different for other spaces like phones or other devices. 20:35 – Advertisement – Sentry – Use the code “devchat” to get two months free on Sentry’s small plan. 21:30 - Aaron asks what decisions around making apps are made by Enact for the developers. Ryan explains that the architectural pattern they have chosen is higher order components, and there is a lot of attention on render props that can be easily plugged into the apps. 22:48 - Aaron asks if the state part was built by the team on their own. Ryan answers in affirmative that everything in Enact is completely built by the team, no external states are used within the framework. No decisions are made in the data space yet. He mentions that they had tried to limit their Enact development effort in cases where the solution was already available unless they had a new perspective on the problem. 24:30 - Aaron remarks the idea of Enact being something like a webpack is becoming clearer for him and asks Ryan if his team is spending most of their time in building component libraries. Ryan affirms by explaining that Enact is designed in layers. He goes on to explain that focus management is a difficult problem to solve where the ability to navigate an application intuitively such as in the case of remote control is handled by a certain component. Also, as LG ships TVs all over the world, there are significant internationalization requirements. He then elucidates the TV centric moonstone library in detail and states that they took all the base capabilities from it and formed a UI layer. 27:26 - Aaron asks if moonstone is theme-able. Ryan says that it’s not and the UI layer in not styled. 28:40 - Chris asks, as someone who manages open source projects and builds tools, about the process of making decisions on the kind of components to include and challenges Ryan and his team faced in the open source space. 29:45 – Ryan says that they haven’t had the ideal open source experience yet. They do have a lot of discussions on API design and components but it’s a struggle to what to include and what to not. 31:25 - Chris shares his own experience while stating that finding a common ground is always hard especially when there is internal resistance in convincing people to use new software. Ryan says that internally their biggest struggle is that a group of people use the Qt platform and there is chunk of webOS that is built on it and not on Enact. Trying to convince people to do the migration from Enyo to Enact was difficult but they have had most success in trying to eliminate friction and it was easier in the sense that there weren’t any required parameters for things. 36:05 – Aaron states that all his questions are answered and his understanding of Enact is clear. 36:21 – Advertisement - Clubhouse 37:10 – Picks! 43:41- END – Advertisement - CacheFly! Picks Joe Monsters of Feyland Chris Presentation by Eric Bailey on Accessibility - If its interactive, it needs a focus style Jimu Robots Wall-E Aimee Coworkers at NPM Aaron Pierogi The Cursed Child Ryan EnactJS Thinking, Fast and Slow Firefox DevTools

JSJ 348: EnactJS with Ryan Duffy

Play Episode Listen Later Jan 22, 2019 44:08

Sponsors KendoUI Sentry use the code "devchat" for $100 credit Clubhouse CacheFly Panel Aimee Knight Aaron Frost Chris Ferdinandi Joe Eames Special Guest: Ryan Duffy In this episode of JavaScript Jabber, the panelists talk with Ryan Duffy who works on the EnactJS framework at LG Electronics. Ryan explains the framework in depth and answers all the questions about its design and implementation from the panelists and discusses some challenges faced along the way. Check it out! Show Notes: 00:28 – Advertisement - KendoUI 1:08 - Ryan introduces himself and explains a bit about the EnactJS framework. While giving some background, he says that it is the 3rd generation of web frameworks that supports apps on webOS and they started building Enact on top of React about two years ago. 2:00 - Aimee asks what exactly does webOS mean. Ryan answers that webOS was created by Palm for phones and related devices and it has several instances of chromium running on device with some service layer stuff. 2:36 - Aaron mentions that webOS was big when other operating systems were still coming up, and Ryan agrees saying that it didn’t get the adoption needed to make it successful later. 3:00 - Ryan says that he always loved building apps for webOS phones given the flexibility and ease coming from a web development background. 3:53 - Aaron asks on which other applications is webOS running other than TV. Ryan answers that TV is one of the major consumptions, and it also runs on certain robots such as the concierge ones, watches to some extent and a lot of projects internally, not yet released in the market. 4:50 - Aaron asks if the Enact framework is big internally at LG. Ryan replies that it is the primary framework used for apps running on webOS. 5:03 - Aaron enquires about the nature of adoption of Enact for third party or non-LG people, to which Ryan states that Enact remains the standard framework for people who are building apps. 5:32 - Joe joins in the conversation. 6:25 - Aaron remarks that given that webOS is used in latest robots, televisions, watches and other such apps, it sounds like they are heavily investing into it. Ryan affirms by saying that the webOS journey goes from Palm phones to HP tablets to finally coming to LG. He goes on to explain their team structure, stating that there are two major teams in play right now - the R&D team is in the US and the implementation team is in Korea. 8:00 - Aaron asks about the role their team plays in the app development. Ryan replies that his team is the stack team that forms the foundation for the apps and they take decisions on what the components should look like and similar tasks. The app teams based in Korea decide their menu based on those decisions. 8:35 - Aaron asks what exactly is meant by the Blink team. Ryan answers that the it’s the team that works with an LG customized version of chromium. 9:10 – Aaron then asks about his individual role in the team. Ryan says that he is one of the managers of the stack team and he’s been on the team for little more than 4 years. 9:30 - Aaron asks about the evolution of the framework over time. Ryan describes the historical background by saying that in the initial Enyo design the team built, was component based, and every tool needed to build single page apps had to be developed from scratch. He says that they felt the need to move on to an improved framework as they wanted to take advantage of the robust ecosystem that existed, so they ported component libraries of Enyo using the React toolset to form Enact. 11:43 - Aaron asks if Enyo then ceased to exist to which Ryan states that it is still around to some extent. 12:20 - Aaron asks if the team has something like “create Enact app” to create a new app internally, like React. Ryan mentions that Jason - a tooling and automation expert from their team has built a feature called V8 snapshot - which loads JavaScript into memory and takes a snapshot - can in turn be loaded by the TV to launch the app in order to achieve a faster load time. He says that their long-term goal is to increase compatibility with the ecosystem. 14:40 - Aaron asks if he can use the React CLI to create something for TV as a third-party developer. Ryan elaborates that CLI can be used to build, compile and bundle apps and there is another tool- SDK to bundle it for delivery to the TV. The app is tested fully in chrome, bundled and deployed to the TV. 15:25 - Aaron asks if choosing React was a natural decision for the team. Ryan explains that they researched on some component-based frameworks that were available at that time and found that React was the best choice. 17:30 - Aimee asks the reason for open sourcing the framework. Ryan mentions that Enyo always has been open source. He also remarks that the team does not get a lot of input from the community and would like to get more information about what’s working and what’s not and how they can contribute back. 19:40 - Aaron asks about the kind of apps can be built by using Enact except for TV. Ryan says that any kind can be built but the hesitation is that the UI library is specially designed for TV, so they may look different for other spaces like phones or other devices. 20:35 – Advertisement – Sentry – Use the code “devchat” to get two months free on Sentry’s small plan. 21:30 - Aaron asks what decisions around making apps are made by Enact for the developers. Ryan explains that the architectural pattern they have chosen is higher order components, and there is a lot of attention on render props that can be easily plugged into the apps. 22:48 - Aaron asks if the state part was built by the team on their own. Ryan answers in affirmative that everything in Enact is completely built by the team, no external states are used within the framework. No decisions are made in the data space yet. He mentions that they had tried to limit their Enact development effort in cases where the solution was already available unless they had a new perspective on the problem. 24:30 - Aaron remarks the idea of Enact being something like a webpack is becoming clearer for him and asks Ryan if his team is spending most of their time in building component libraries. Ryan affirms by explaining that Enact is designed in layers. He goes on to explain that focus management is a difficult problem to solve where the ability to navigate an application intuitively such as in the case of remote control is handled by a certain component. Also, as LG ships TVs all over the world, there are significant internationalization requirements. He then elucidates the TV centric moonstone library in detail and states that they took all the base capabilities from it and formed a UI layer. 27:26 - Aaron asks if moonstone is theme-able. Ryan says that it’s not and the UI layer in not styled. 28:40 - Chris asks, as someone who manages open source projects and builds tools, about the process of making decisions on the kind of components to include and challenges Ryan and his team faced in the open source space. 29:45 – Ryan says that they haven’t had the ideal open source experience yet. They do have a lot of discussions on API design and components but it’s a struggle to what to include and what to not. 31:25 - Chris shares his own experience while stating that finding a common ground is always hard especially when there is internal resistance in convincing people to use new software. Ryan says that internally their biggest struggle is that a group of people use the Qt platform and there is chunk of webOS that is built on it and not on Enact. Trying to convince people to do the migration from Enyo to Enact was difficult but they have had most success in trying to eliminate friction and it was easier in the sense that there weren’t any required parameters for things. 36:05 – Aaron states that all his questions are answered and his understanding of Enact is clear. 36:21 – Advertisement - Clubhouse 37:10 – Picks! 43:41- END – Advertisement - CacheFly! Picks Joe Monsters of Feyland Chris Presentation by Eric Bailey on Accessibility - If its interactive, it needs a focus style Jimu Robots Wall-E Aimee Coworkers at NPM Aaron Pierogi The Cursed Child Ryan EnactJS Thinking, Fast and Slow Firefox DevTools

JSJ 348: EnactJS with Ryan Duffy

Play Episode Listen Later Jan 22, 2019 44:08

Sponsors KendoUI Sentry use the code "devchat" for $100 credit Clubhouse CacheFly Panel Aimee Knight Aaron Frost Chris Ferdinandi Joe Eames Special Guest: Ryan Duffy In this episode of JavaScript Jabber, the panelists talk with Ryan Duffy who works on the EnactJS framework at LG Electronics. Ryan explains the framework in depth and answers all the questions about its design and implementation from the panelists and discusses some challenges faced along the way. Check it out! Show Notes: 00:28 – Advertisement - KendoUI 1:08 - Ryan introduces himself and explains a bit about the EnactJS framework. While giving some background, he says that it is the 3rd generation of web frameworks that supports apps on webOS and they started building Enact on top of React about two years ago. 2:00 - Aimee asks what exactly does webOS mean. Ryan answers that webOS was created by Palm for phones and related devices and it has several instances of chromium running on device with some service layer stuff. 2:36 - Aaron mentions that webOS was big when other operating systems were still coming up, and Ryan agrees saying that it didn’t get the adoption needed to make it successful later. 3:00 - Ryan says that he always loved building apps for webOS phones given the flexibility and ease coming from a web development background. 3:53 - Aaron asks on which other applications is webOS running other than TV. Ryan answers that TV is one of the major consumptions, and it also runs on certain robots such as the concierge ones, watches to some extent and a lot of projects internally, not yet released in the market. 4:50 - Aaron asks if the Enact framework is big internally at LG. Ryan replies that it is the primary framework used for apps running on webOS. 5:03 - Aaron enquires about the nature of adoption of Enact for third party or non-LG people, to which Ryan states that Enact remains the standard framework for people who are building apps. 5:32 - Joe joins in the conversation. 6:25 - Aaron remarks that given that webOS is used in latest robots, televisions, watches and other such apps, it sounds like they are heavily investing into it. Ryan affirms by saying that the webOS journey goes from Palm phones to HP tablets to finally coming to LG. He goes on to explain their team structure, stating that there are two major teams in play right now - the R&D team is in the US and the implementation team is in Korea. 8:00 - Aaron asks about the role their team plays in the app development. Ryan replies that his team is the stack team that forms the foundation for the apps and they take decisions on what the components should look like and similar tasks. The app teams based in Korea decide their menu based on those decisions. 8:35 - Aaron asks what exactly is meant by the Blink team. Ryan answers that the it’s the team that works with an LG customized version of chromium. 9:10 – Aaron then asks about his individual role in the team. Ryan says that he is one of the managers of the stack team and he’s been on the team for little more than 4 years. 9:30 - Aaron asks about the evolution of the framework over time. Ryan describes the historical background by saying that in the initial Enyo design the team built, was component based, and every tool needed to build single page apps had to be developed from scratch. He says that they felt the need to move on to an improved framework as they wanted to take advantage of the robust ecosystem that existed, so they ported component libraries of Enyo using the React toolset to form Enact. 11:43 - Aaron asks if Enyo then ceased to exist to which Ryan states that it is still around to some extent. 12:20 - Aaron asks if the team has something like “create Enact app” to create a new app internally, like React. Ryan mentions that Jason - a tooling and automation expert from their team has built a feature called V8 snapshot - which loads JavaScript into memory and takes a snapshot - can in turn be loaded by the TV to launch the app in order to achieve a faster load time. He says that their long-term goal is to increase compatibility with the ecosystem. 14:40 - Aaron asks if he can use the React CLI to create something for TV as a third-party developer. Ryan elaborates that CLI can be used to build, compile and bundle apps and there is another tool- SDK to bundle it for delivery to the TV. The app is tested fully in chrome, bundled and deployed to the TV. 15:25 - Aaron asks if choosing React was a natural decision for the team. Ryan explains that they researched on some component-based frameworks that were available at that time and found that React was the best choice. 17:30 - Aimee asks the reason for open sourcing the framework. Ryan mentions that Enyo always has been open source. He also remarks that the team does not get a lot of input from the community and would like to get more information about what’s working and what’s not and how they can contribute back. 19:40 - Aaron asks about the kind of apps can be built by using Enact except for TV. Ryan says that any kind can be built but the hesitation is that the UI library is specially designed for TV, so they may look different for other spaces like phones or other devices. 20:35 – Advertisement – Sentry – Use the code “devchat” to get two months free on Sentry’s small plan. 21:30 - Aaron asks what decisions around making apps are made by Enact for the developers. Ryan explains that the architectural pattern they have chosen is higher order components, and there is a lot of attention on render props that can be easily plugged into the apps. 22:48 - Aaron asks if the state part was built by the team on their own. Ryan answers in affirmative that everything in Enact is completely built by the team, no external states are used within the framework. No decisions are made in the data space yet. He mentions that they had tried to limit their Enact development effort in cases where the solution was already available unless they had a new perspective on the problem. 24:30 - Aaron remarks the idea of Enact being something like a webpack is becoming clearer for him and asks Ryan if his team is spending most of their time in building component libraries. Ryan affirms by explaining that Enact is designed in layers. He goes on to explain that focus management is a difficult problem to solve where the ability to navigate an application intuitively such as in the case of remote control is handled by a certain component. Also, as LG ships TVs all over the world, there are significant internationalization requirements. He then elucidates the TV centric moonstone library in detail and states that they took all the base capabilities from it and formed a UI layer. 27:26 - Aaron asks if moonstone is theme-able. Ryan says that it’s not and the UI layer in not styled. 28:40 - Chris asks, as someone who manages open source projects and builds tools, about the process of making decisions on the kind of components to include and challenges Ryan and his team faced in the open source space. 29:45 – Ryan says that they haven’t had the ideal open source experience yet. They do have a lot of discussions on API design and components but it’s a struggle to what to include and what to not. 31:25 - Chris shares his own experience while stating that finding a common ground is always hard especially when there is internal resistance in convincing people to use new software. Ryan says that internally their biggest struggle is that a group of people use the Qt platform and there is chunk of webOS that is built on it and not on Enact. Trying to convince people to do the migration from Enyo to Enact was difficult but they have had most success in trying to eliminate friction and it was easier in the sense that there weren’t any required parameters for things. 36:05 – Aaron states that all his questions are answered and his understanding of Enact is clear. 36:21 – Advertisement - Clubhouse 37:10 – Picks! 43:41- END – Advertisement - CacheFly! Picks Joe Monsters of Feyland Chris Presentation by Eric Bailey on Accessibility - If its interactive, it needs a focus style Jimu Robots Wall-E Aimee Coworkers at NPM Aaron Pierogi The Cursed Child Ryan EnactJS Thinking, Fast and Slow Firefox DevTools

JSJ 347: JAMstack with Divya Sasidharan & Phil Hawksworth

Play Episode Listen Later Jan 15, 2019 81:54

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Chris Ferdinandi Charles Max Wood Joined by special guest: Phil Hawksworth and Divya Sasidharan Episode Summary This episode features special guests Philip Hawksworth and Divya Sasidharan. Phil lives just outside of London and Divya lives in Chicago, and both of them work for Netlify. Divya is also a regular on the Devchat show Views on Vue. The panelists begin by discussing what JAMstack is. JAM stands for JavaScript, API, and Markup. It used to be known as the new name for static sites, but it’s much more than that. Phil talks about how dynamic ‘static’ sites really are. JAMstack sites range from very simple to very complex, Static is actually a misnomer. JAMstack makes making, deploying, and publishing as simple as possible. The panelists discuss the differences between building your own API and JAMstack and how JavaScript fits into the JAMstack ecosystem. They talk about keys and secrets in APIs and the best way to handle credentials in a static site. There are multiple ways to handle it, but Netlify has some built in solutions. All you have to do is write your logic for what you want your function to do and what packages you want included in it, they do all the rest. Every deployment you make stays there, so you can always roll back to a previous version. Charles asks about how to convert a website that’s built on a CMS to a static site and some of the tools available on Netlify. They finish by discussing different hangups on migrating platforms for things like Devchat (which is built on WordPress) and the benefits of switching servers. Links API React JAMstack CMS (content management system) CDM (Customer Data Management) Markup UI (User Interface) Jekyll Progressive Enhancement 11ty Hugo React Static Gatsby Vue AWS AWS Lambda Azure Markdown WordPress Zapier Stefan Baumgartner article RSS feed Picks AJ O’Neal: Prince Ali Ababwa (Aladdin) Node v.10.12 Chris Ferdinandi: Bouncer Philip Morgan Consulting Jonathan Stark Consulting Charles Max Wood: Mastadon Social Thanksgiving turkey Phil Hawksworth: Dripping (solidified meat drippings spread on toast) They Shall Not Grow Old Divya Sasidharan: Fear, Trust, and JavaScript Women’s Pockets Are Inferior Debt: A Love Story

women fear thanksgiving trust chicago panel clubhouse views react wordpress jam api aws apis static cms jekyll javascript azure zapier node gatsby vue divya sentry dripping bouncer markdown markup netlify aws lambda they shall not grow old jamstack devchat charles max wood chris ferdinandi progressive enhancement kendo ui ui user interface phil hawksworth divya sasidharan stefan baumgartner philip morgan consulting

JSJ 347: JAMstack with Divya Sasidharan & Phil Hawksworth

Play Episode Listen Later Jan 15, 2019 81:54

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Chris Ferdinandi Charles Max Wood Joined by special guest: Phil Hawksworth and Divya Sasidharan Episode Summary This episode features special guests Philip Hawksworth and Divya Sasidharan. Phil lives just outside of London and Divya lives in Chicago, and both of them work for Netlify. Divya is also a regular on the Devchat show Views on Vue. The panelists begin by discussing what JAMstack is. JAM stands for JavaScript, API, and Markup. It used to be known as the new name for static sites, but it’s much more than that. Phil talks about how dynamic ‘static’ sites really are. JAMstack sites range from very simple to very complex, Static is actually a misnomer. JAMstack makes making, deploying, and publishing as simple as possible. The panelists discuss the differences between building your own API and JAMstack and how JavaScript fits into the JAMstack ecosystem. They talk about keys and secrets in APIs and the best way to handle credentials in a static site. There are multiple ways to handle it, but Netlify has some built in solutions. All you have to do is write your logic for what you want your function to do and what packages you want included in it, they do all the rest. Every deployment you make stays there, so you can always roll back to a previous version. Charles asks about how to convert a website that’s built on a CMS to a static site and some of the tools available on Netlify. They finish by discussing different hangups on migrating platforms for things like Devchat (which is built on WordPress) and the benefits of switching servers. Links API React JAMstack CMS (content management system) CDM (Customer Data Management) Markup UI (User Interface) Jekyll Progressive Enhancement 11ty Hugo React Static Gatsby Vue AWS AWS Lambda Azure Markdown WordPress Zapier Stefan Baumgartner article RSS feed Picks AJ O’Neal: Prince Ali Ababwa (Aladdin) Node v.10.12 Chris Ferdinandi: Bouncer Philip Morgan Consulting Jonathan Stark Consulting Charles Max Wood: Mastadon Social Thanksgiving turkey Phil Hawksworth: Dripping (solidified meat drippings spread on toast) They Shall Not Grow Old Divya Sasidharan: Fear, Trust, and JavaScript Women’s Pockets Are Inferior Debt: A Love Story

women fear thanksgiving trust chicago panel clubhouse views react wordpress jam api aws apis static cms jekyll javascript azure zapier node gatsby vue divya sentry dripping bouncer markdown markup netlify aws lambda they shall not grow old jamstack devchat charles max wood chris ferdinandi progressive enhancement kendo ui ui user interface phil hawksworth divya sasidharan stefan baumgartner philip morgan consulting

JSJ 347: JAMstack with Divya Sasidharan & Phil Hawksworth

Play Episode Listen Later Jan 15, 2019 81:54

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Chris Ferdinandi Charles Max Wood Joined by special guest: Phil Hawksworth and Divya Sasidharan Episode Summary This episode features special guests Philip Hawksworth and Divya Sasidharan. Phil lives just outside of London and Divya lives in Chicago, and both of them work for Netlify. Divya is also a regular on the Devchat show Views on Vue. The panelists begin by discussing what JAMstack is. JAM stands for JavaScript, API, and Markup. It used to be known as the new name for static sites, but it’s much more than that. Phil talks about how dynamic ‘static’ sites really are. JAMstack sites range from very simple to very complex, Static is actually a misnomer. JAMstack makes making, deploying, and publishing as simple as possible. The panelists discuss the differences between building your own API and JAMstack and how JavaScript fits into the JAMstack ecosystem. They talk about keys and secrets in APIs and the best way to handle credentials in a static site. There are multiple ways to handle it, but Netlify has some built in solutions. All you have to do is write your logic for what you want your function to do and what packages you want included in it, they do all the rest. Every deployment you make stays there, so you can always roll back to a previous version. Charles asks about how to convert a website that’s built on a CMS to a static site and some of the tools available on Netlify. They finish by discussing different hangups on migrating platforms for things like Devchat (which is built on WordPress) and the benefits of switching servers. Links API React JAMstack CMS (content management system) CDM (Customer Data Management) Markup UI (User Interface) Jekyll Progressive Enhancement 11ty Hugo React Static Gatsby Vue AWS AWS Lambda Azure Markdown WordPress Zapier Stefan Baumgartner article RSS feed Picks AJ O’Neal: Prince Ali Ababwa (Aladdin) Node v.10.12 Chris Ferdinandi: Bouncer Philip Morgan Consulting Jonathan Stark Consulting Charles Max Wood: Mastadon Social Thanksgiving turkey Phil Hawksworth: Dripping (solidified meat drippings spread on toast) They Shall Not Grow Old Divya Sasidharan: Fear, Trust, and JavaScript Women’s Pockets Are Inferior Debt: A Love Story

women fear thanksgiving trust chicago panel clubhouse views react wordpress jam api aws apis static cms jekyll javascript azure zapier node gatsby vue divya sentry dripping bouncer markdown markup netlify aws lambda they shall not grow old jamstack devchat charles max wood chris ferdinandi progressive enhancement kendo ui ui user interface phil hawksworth divya sasidharan stefan baumgartner philip morgan consulting

VoV 044: Nuxt.js with Alexander Lichter

Play Episode Listen Later Jan 15, 2019 41:26

Sponsors KendoUI Sentry use the code "devchat" for 2 months free on Sentry small plan TripleByte CacheFly Panel Joe Eames Charles Max Wood Joined by Special Guest: Alexander Lichter Summary Alexander Lichter introduces Nuxt.js, explaining how to use it and what use cases it can be used for. He explains why a developer should learn Nuxt.js and advises on a few learning resources. The panel discusses statically rendered sites and server-side rendering. Alexander shares what’s next for Nuxt.js and what to expect in the newest version. As a core team member at age 21, Alexander explains how he got involved with the Nuxt.js team. The panel shares an appreciation that anyone with any amount of experience can contribute to open source. Alexander shares a little about his own life and what is “nuxt” for him. Links https://school.programwitherik.com/p/create-awesome-vue-js-apps-with-nuxt-js https://devchat.tv/dev-rev/ https://nuxtjs.org/ https://vueschool.io/ https://www.lichter.io/ https://twitter.com/TheAlexLichter https://github.com/manniL https://www.facebook.com/ViewsonVue https://twitter.com/viewsonvue Picks Joe Eames: https://vueschool.io/ https://serviceworkies.com/ Charles Max Wood: Disney Heroes: Battle Mode The Immortal Nicholas Alexander Lichter: http://www.brainerrors.com/anchoringeffect-gandhi.php https://medium.com/@vipercodegames/nuxt-deploy-809eda0168fc

panel lichter sentry cachefly nuxt charles max wood triplebyte kendo ui joe eames disney heroes battle mode

RRU 044: TypeScript with Spencer Miskoviak

Play Episode Listen Later Jan 15, 2019 44:29

Sponsors KendoUI Sentry use the code “devchat” for $100 credit TripleByte CacheFly Panel Charles Max Wood Nader Dabit JC Hiatt Joined by Special Guest: Spencer Miskoviak Summary In this episode, Spencer Miskoviak shares his experience and answers questions about using typescript in React. Spencer starts by answering why react developers tend to use es6 and what the tradeoff is using typescript instead. The panel contemplates the advantages and disadvantages of using typescript and its gaining momentum in the React community. Spencer discusses how they are using typescript at Handshake and how it has paid off. Create react app and its support of typescript is discussed. The episode ends with Spencer answering questions about using dot notation with typescript and how it works. Links https://webpack.js.org/ https://parceljs.org/ https://medium.com/@skovy/using-component-dot-notation-with-typescript-to-create-a-set-of-components-b0b2aad4892b https://app.joinhandshake.com/login https://medium.com/@skovy https://twitter.com/SpencerSkovy https://github.com/Skovy Picks Nader Dabit https://medium.com/open-graphql https://reinvent.awsevents.com/ JC Hiatt Sony Noise Cancelling Headphones WH1000XM3 Charles Max Wood https://devchat.tv/dev-rev/ https://www.garyvaynerchuk.com/podcast/ https://player.fm/series/refactor-your-body Spencer Miskoviak http://www.rubberducking.fm/ The Future of React Endurance: My Year in Space, A Lifetime of Discovery by Scott Kelly

future space discovery lifetime panel react handshakes sentry typescript scott kelly cachefly nader dabit charles max wood triplebyte kendo ui jc hiatt

VoV 044: Nuxt.js with Alexander Lichter

Play Episode Listen Later Jan 15, 2019 41:26

Sponsors KendoUI Sentry use the code "devchat" for 2 months free on Sentry small plan TripleByte CacheFly Panel Joe Eames Charles Max Wood Joined by Special Guest: Alexander Lichter Summary Alexander Lichter introduces Nuxt.js, explaining how to use it and what use cases it can be used for. He explains why a developer should learn Nuxt.js and advises on a few learning resources. The panel discusses statically rendered sites and server-side rendering. Alexander shares what’s next for Nuxt.js and what to expect in the newest version. As a core team member at age 21, Alexander explains how he got involved with the Nuxt.js team. The panel shares an appreciation that anyone with any amount of experience can contribute to open source. Alexander shares a little about his own life and what is “nuxt” for him. Links https://school.programwitherik.com/p/create-awesome-vue-js-apps-with-nuxt-js https://devchat.tv/dev-rev/ https://nuxtjs.org/ https://vueschool.io/ https://www.lichter.io/ https://twitter.com/TheAlexLichter https://github.com/manniL https://www.facebook.com/ViewsonVue https://twitter.com/viewsonvue Picks Joe Eames: https://vueschool.io/ https://serviceworkies.com/ Charles Max Wood: Disney Heroes: Battle Mode The Immortal Nicholas Alexander Lichter: http://www.brainerrors.com/anchoringeffect-gandhi.php https://medium.com/@vipercodegames/nuxt-deploy-809eda0168fc

panel lichter sentry cachefly nuxt charles max wood triplebyte kendo ui joe eames disney heroes battle mode

RRU 044: TypeScript with Spencer Miskoviak

Play Episode Listen Later Jan 15, 2019 44:29

Sponsors KendoUI Sentry use the code “devchat” for $100 credit TripleByte CacheFly Panel Charles Max Wood Nader Dabit JC Hiatt Joined by Special Guest: Spencer Miskoviak Summary In this episode, Spencer Miskoviak shares his experience and answers questions about using typescript in React. Spencer starts by answering why react developers tend to use es6 and what the tradeoff is using typescript instead. The panel contemplates the advantages and disadvantages of using typescript and its gaining momentum in the React community. Spencer discusses how they are using typescript at Handshake and how it has paid off. Create react app and its support of typescript is discussed. The episode ends with Spencer answering questions about using dot notation with typescript and how it works. Links https://webpack.js.org/ https://parceljs.org/ https://medium.com/@skovy/using-component-dot-notation-with-typescript-to-create-a-set-of-components-b0b2aad4892b https://app.joinhandshake.com/login https://medium.com/@skovy https://twitter.com/SpencerSkovy https://github.com/Skovy Picks Nader Dabit https://medium.com/open-graphql https://reinvent.awsevents.com/ JC Hiatt Sony Noise Cancelling Headphones WH1000XM3 Charles Max Wood https://devchat.tv/dev-rev/ https://www.garyvaynerchuk.com/podcast/ https://player.fm/series/refactor-your-body Spencer Miskoviak http://www.rubberducking.fm/ The Future of React Endurance: My Year in Space, A Lifetime of Discovery by Scott Kelly

future space discovery lifetime panel react handshakes sentry typescript scott kelly cachefly nader dabit charles max wood triplebyte kendo ui jc hiatt

JSJ 346: Azure Pipelines with Ed Thomson LIVE at Microsoft Ignite

Play Episode Listen Later Jan 8, 2019 43:19

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck: How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools. 41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Picks: Ed Podcast - All Things Git

live google microsoft phone android panel clubhouse windows reduce developers releases special guests pipeline ignite github blackberry program managers javascript devops macos azure rewind apache zip pipelines git advertisement sentry onedrive freshbooks repos digital ocean vs code ionic microsoft ignite erlang fsf azure devops dotnet edone repositories emac ed it charles max wood app center azure pipelines cd pipeline chuck it kendo ui whitesource chuck you chuck how ed thomson chuck let ed you visual code us 2528sem 2529branded 257cexm ed don ed they ed let ed yes chuck where chuck any chuck yes chuck people ed just google azure brand ed exactly ed here chuck beyond ed pipelines chuck then ed depends raspberries pies visual studio code because ed now ed that chuck chuck dude podcast all things git ocid aid719825 sem fnqqigda chuck vpn ed once chuck repos ed technically chuck testing

JSJ 346: Azure Pipelines with Ed Thomson LIVE at Microsoft Ignite

Play Episode Listen Later Jan 8, 2019 43:19

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck: How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools. 41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Picks: Ed Podcast - All Things Git

live google microsoft phone android panel clubhouse windows reduce developers releases special guests pipeline ignite github blackberry program managers javascript devops macos azure rewind apache zip pipelines git advertisement sentry onedrive freshbooks repos digital ocean vs code ionic microsoft ignite erlang fsf azure devops dotnet edone repositories emac ed it charles max wood app center azure pipelines cd pipeline chuck it kendo ui whitesource chuck you chuck how ed thomson chuck let ed you visual code us 2528sem 2529branded 257cexm ed don ed they ed let ed yes chuck where chuck any chuck yes chuck people ed just google azure brand ed exactly ed here chuck beyond ed pipelines chuck then ed depends raspberries pies visual studio code because ed now chuck dude ed that chuck ocid aid719825 sem fnqqigda podcast all things git chuck vpn ed once chuck repos ed technically chuck testing

JSJ 346: Azure Pipelines with Ed Thomson LIVE at Microsoft Ignite

Play Episode Listen Later Jan 8, 2019 43:19

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck: How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools. 41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Picks: Ed Podcast - All Things Git

live google microsoft phone android panel clubhouse windows reduce developers releases special guests pipeline ignite github blackberry program managers javascript devops macos azure rewind apache zip pipelines git advertisement sentry onedrive freshbooks repos digital ocean vs code ionic microsoft ignite erlang fsf azure devops dotnet edone repositories emac ed it charles max wood app center azure pipelines cd pipeline chuck it kendo ui whitesource chuck you chuck how ed thomson chuck let ed you visual code us 2528sem 2529branded 257cexm ed don ed they ed let ed yes chuck where chuck any chuck yes chuck people ed just google azure brand ed exactly ed here chuck beyond ed pipelines chuck then ed depends raspberries pies visual studio code because ed now chuck dude ed that chuck ocid aid719825 sem fnqqigda podcast all things git chuck vpn ed once chuck repos ed technically chuck testing

RRU 043: Testing React Apps Without Testing Implementation Details with Kent C. Dodds

Play Episode Listen Later Dec 25, 2018 75:55

Panel: Lucas Reis Justin Bennett Charles Max Wood Special Guest: Kent C. Dodds In this episode, the panelist talk with today’s guest, Kent C. Dodds who works for PayPal, is an instructor, and works through open source! Kent lives in Utah with his wife and four children. Kent and the panel talk today about testing – check it out! Show Topics: 0:00 – Kendo UI 0:32 – Chuck: Hello! My new show is TheDevRev – please go check it out! 1:35 – Panel: I want all of it! 1:43 – Chuck: Our guest is Kent C. Dodds! You were on the show for a while and then you got busy. 2:06 – Guest. 3:09 – Panel: The kid part is impressive. 3:20 – Guest: Yeah it’s awesome, but the kid part is my wife! 4:09 – Panel: 10 years ago we weren’t having any tests and then now we are thinking about how to write better tests. It’s the next step on that subject. What is your story with tests and what sparked these ideas? 4:50 – Guest. 7:25 – Panel: We have a bunch of tests at my work. “There is no such thing as too many tests” are being said a lot! Then we started talking about unit tests and there was this shift. The tests, for me, felt cumbersome. How do I know that this suite of tests are actually helping me and not hurting me? 8:32 – Guest: I think that is a valuable insight. 11:03 – Panel: What is the make-up of a good test? 11:13 – Guest: Test every line – everything! No. 11:19 – Chuck: “Look at everything!” I don’t know where to start, man! 11:30 – Guest: How do you avoid those false negatives and false positives. 15:38 – Panel: The end user is going to be like more of integration test, and the developer user will be more like a unit tester? 16:01 – Guest: I don’t care too much of the distinction between unit and integration tests. 18:36 – Panel: I have worked in testing in the past. One of the big things that fall on the users’ flow is that it’s difficult b/c maybe a tool like Selenium: when will things render? Are you still testing things in isolation? 19:33 – Guest: It depends. When I talk about UI integration testing I am still mocking the backend. 23:10 – Chuck: I am curious, where do you decide these are expensive (so I don’t want to do too many of them), but at what point is it worth it to do it? 23:30 – Guest mentions the testing pyramid. 28:14 – Chuck: Why do you care about confidence? What is confidence and what does it matter? 28:35 – FreshBooks! 29:50 – Guest. 32:20 – Panel: I have something to add about the testing pyramid. Lucas talks about tooling, Mocha, JS Dong, and more! 33:44 – Guest: I think the testing pyramid is outdated and I have created my own. Guest talks about static testing, LINT, Cypress, and more! 35:32 – Chuck: When I was a new developer, people talked about using tests to track down bugs. What if it’s a hairy bug? 36:07 – Guest: If you can, you can use this methodical approach... 39:46 – Panel: Let’s talk about the React library for a little bit? Panel: Part of the confidence of the tests we write we ask ourselves “will it stand the test of time?” How does the React Testing library go about to solve that? 41:05 – Guest. 47:51 – Panel: A few more questions. When you are getting something and testing and grabbing the label by its text have you found that to be fragile? Is it reasonably reliable? 48:57 – Guest: Yeah this is a concern and it relies on content. 53:06 – Panel: I like this idea of having a different library. Sometimes we think that a powerful tool is better, but after spending some time with other tools that’s not always the case. 54:16 – Guest: “You tie your hands to free your mind.” It does less but what it does less it does better. 55:42 – Panel: I think that with Cypress, too? 55:51 – Guest: Yeah that’s why Cypress is great to use. 57:17 – Panel: I wrote a small library here at work and it deals with metrics. I automated all of those small clicks – write a bit – click a bit – and it was really good. I felt quite efficient. Those became the tests. 57:58 – Panel: One more question: What about react Native? That comes up a lot. At looking at testing libraries we try to keep parody between the two. Do you have any thoughts on that? 58:34 – Guest talks about React Native. 1:00:22 – Panel: Anything else? It’s fascinating to talk about and dive-into these topics. When we talk about confidence that is very powerful, too. 1:01:02 – Panelist asks the last question! 1:01:38 – Guest: You could show them the coverage support. Links: Ruby on Rails Angular JavaScript Elm Phoenix GitHub Get A Coder Job Enzyme React Testing Library Cypress.io Hillel Wayne Testing JavaScript with Kent C. Dodds Kent Dodds’ News Kent Dodds’ Blog Egghead.io – Kent C. Dodds Ready to Write a Novel? Practical TLA+ GitHub: Circleci-queue GitHub: sstephenson / bats Todoist Discord Kent’s Twitter Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI Picks: Lucas Hillel Wayne Practical TLA+ Justin Circle CI Queue Bats Todoists Charles MFCEO Project Podcast The DevRev Kent Discord Devs Who Write Finding your Why! TestingJavaScript.com kcd.im/news kcd.i./hooks-and-suspense NaNoWriMo

google news write blog utah testing discord apps panel paypal kent react bats implementation ui github javascript rails panelists elm nanowrimo cypress angular mocha ruby on rails dodds freshbooks enzyme todoist selenium eggheads react native cachefly kent c dodds panel one charles max wood justin bennett devrev kendo ui mfceo project podcast lucas reis hillel wayne coder job chuck why get a coder job us 2528sem 2529branded 257cexm panel let react testing 257efreshbooks thedevrev panel anything

RRU 043: Testing React Apps Without Testing Implementation Details with Kent C. Dodds

The Polyglot Developer Podcast

Play Episode Listen Later Dec 25, 2018 75:55

Panel: Lucas Reis Justin Bennett Charles Max Wood Special Guest: Kent C. Dodds In this episode, the panelist talk with today’s guest, Kent C. Dodds who works for PayPal, is an instructor, and works through open source! Kent lives in Utah with his wife and four children. Kent and the panel talk today about testing – check it out! Show Topics: 0:00 – Kendo UI 0:32 – Chuck: Hello! My new show is TheDevRev – please go check it out! 1:35 – Panel: I want all of it! 1:43 – Chuck: Our guest is Kent C. Dodds! You were on the show for a while and then you got busy. 2:06 – Guest. 3:09 – Panel: The kid part is impressive. 3:20 – Guest: Yeah it’s awesome, but the kid part is my wife! 4:09 – Panel: 10 years ago we weren’t having any tests and then now we are thinking about how to write better tests. It’s the next step on that subject. What is your story with tests and what sparked these ideas? 4:50 – Guest. 7:25 – Panel: We have a bunch of tests at my work. “There is no such thing as too many tests” are being said a lot! Then we started talking about unit tests and there was this shift. The tests, for me, felt cumbersome. How do I know that this suite of tests are actually helping me and not hurting me? 8:32 – Guest: I think that is a valuable insight. 11:03 – Panel: What is the make-up of a good test? 11:13 – Guest: Test every line – everything! No. 11:19 – Chuck: “Look at everything!” I don’t know where to start, man! 11:30 – Guest: How do you avoid those false negatives and false positives. 15:38 – Panel: The end user is going to be like more of integration test, and the developer user will be more like a unit tester? 16:01 – Guest: I don’t care too much of the distinction between unit and integration tests. 18:36 – Panel: I have worked in testing in the past. One of the big things that fall on the users’ flow is that it’s difficult b/c maybe a tool like Selenium: when will things render? Are you still testing things in isolation? 19:33 – Guest: It depends. When I talk about UI integration testing I am still mocking the backend. 23:10 – Chuck: I am curious, where do you decide these are expensive (so I don’t want to do too many of them), but at what point is it worth it to do it? 23:30 – Guest mentions the testing pyramid. 28:14 – Chuck: Why do you care about confidence? What is confidence and what does it matter? 28:35 – FreshBooks! 29:50 – Guest. 32:20 – Panel: I have something to add about the testing pyramid. Lucas talks about tooling, Mocha, JS Dong, and more! 33:44 – Guest: I think the testing pyramid is outdated and I have created my own. Guest talks about static testing, LINT, Cypress, and more! 35:32 – Chuck: When I was a new developer, people talked about using tests to track down bugs. What if it’s a hairy bug? 36:07 – Guest: If you can, you can use this methodical approach... 39:46 – Panel: Let’s talk about the React library for a little bit? Panel: Part of the confidence of the tests we write we ask ourselves “will it stand the test of time?” How does the React Testing library go about to solve that? 41:05 – Guest. 47:51 – Panel: A few more questions. When you are getting something and testing and grabbing the label by its text have you found that to be fragile? Is it reasonably reliable? 48:57 – Guest: Yeah this is a concern and it relies on content. 53:06 – Panel: I like this idea of having a different library. Sometimes we think that a powerful tool is better, but after spending some time with other tools that’s not always the case. 54:16 – Guest: “You tie your hands to free your mind.” It does less but what it does less it does better. 55:42 – Panel: I think that with Cypress, too? 55:51 – Guest: Yeah that’s why Cypress is great to use. 57:17 – Panel: I wrote a small library here at work and it deals with metrics. I automated all of those small clicks – write a bit – click a bit – and it was really good. I felt quite efficient. Those became the tests. 57:58 – Panel: One more question: What about react Native? That comes up a lot. At looking at testing libraries we try to keep parody between the two. Do you have any thoughts on that? 58:34 – Guest talks about React Native. 1:00:22 – Panel: Anything else? It’s fascinating to talk about and dive-into these topics. When we talk about confidence that is very powerful, too. 1:01:02 – Panelist asks the last question! 1:01:38 – Guest: You could show them the coverage support. Links: Ruby on Rails Angular JavaScript Elm Phoenix GitHub Get A Coder Job Enzyme React Testing Library Cypress.io Hillel Wayne Testing JavaScript with Kent C. Dodds Kent Dodds’ News Kent Dodds’ Blog Egghead.io – Kent C. Dodds Ready to Write a Novel? Practical TLA+ GitHub: Circleci-queue GitHub: sstephenson / bats Todoist Discord Kent’s Twitter Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI Picks: Lucas Hillel Wayne Practical TLA+ Justin Circle CI Queue Bats Todoists Charles MFCEO Project Podcast The DevRev Kent Discord Devs Who Write Finding your Why! TestingJavaScript.com kcd.im/news kcd.i./hooks-and-suspense NaNoWriMo

google news write blog utah testing discord apps panel paypal kent react bats implementation ui github javascript rails panelists elm nanowrimo cypress angular mocha ruby on rails dodds freshbooks enzyme todoist selenium eggheads react native cachefly kent c dodds panel one charles max wood justin bennett devrev kendo ui mfceo project podcast lucas reis hillel wayne coder job chuck why get a coder job us 2528sem 2529branded 257cexm panel let react testing 257efreshbooks thedevrev panel anything

TPDP005: Developing Mobile Apps with Telerik NativeScript

Play Episode Listen Later May 10, 2016 50:30

In this episode I'm joined by TJ VanToll, Developer Advocate at Telerik, where we discuss the cross platform mobile development framework NativeScript. We cover everything from what is NativeScript, what do you need to start developing NativeScript applications, and how it differs or why you should use it versus native development or development with a different hybrid mobile framework. TJ talks about where things are headed when it comes to mobile development, who is using Telerik NativeScript to develop apps, and how Angular 2 fits into the framework. This is the most exciting episode yet on The Polyglot Developer Podcast and I recommend listening to it if you're interested in mobile application development, whether it be for personal or for your business. A writeup to this episode can be found via https://www.thepolyglotdeveloper.com/2016/05/tpdp-episode-5-developing-mobile-apps-telerik-nativescript/ on my blog. If you have questions that you'd like answered in the next episode, visit https://www.thepolyglotdeveloper.com/podcast-questions and fill out the form.

developing android mobile apps ios javascript css mobile apps angular developer advocate angularjs nativescript telerik kendo ui tj vantoll

36: Understanding PhoneGap

The Web Platform Podcast

Play Episode Listen Later Mar 24, 2015 57:51

Brian Leroux (@brianleroux), Adobe Phonegap Team Member & open source software developer, spends lots of time on the Apache Cordova and Adobe PhoneGap projects. Hailing from Canada, he loves his hockey and beer- maybe even more than coding. He has spoken at many conferences and is an expert in delivering & teaching mobile web development. Brian goes into depth on the Phonegap project. Brian discusses how developers can get started building great mobile experiences with Phonegap. He also details the benefits / downfalls of different approaches to mobile development using web technologies as well as tooling, testing, and automation. Resources PhoneGap - https://phonegap.com PhoneGap Build - https://build.phonegap.com/ Ionic Framework - http://ionicframework.com/ Cordova - https://cordova.apache.org/ Introduction to PhoneGap Build - http://tv.adobe.com/watch/building-mobile-apps-with-phonegap-build/introduction-to-phonegap-build-building-your-first-app/ Kony - http://www.kony.com/ ReApp - http://reapp.io/ Appcelerator - http://www.appcelerator.com/ Sencha Touch - http://www.sencha.com/products/touch JQuery Mobile - http://jquerymobile.com/ Kendo UI - http://www.telerik.com/kendo-ui Onsen UI - http://onsen.io/ Famo.us - https://famo.us/ Firefox OS - https://www.mozilla.org/en-US/firefox/os/ Crosswalk - https://crosswalk-project.org/ ReApp - http://reapp.io/ Phonegap Experts (company) - ` http://phonegapexperts.com/?gclid=CjwKEAjw876oBRCYr86w6KGfpkgSJAACIidwP41ihwn_EWhsPDM_3QAL5hG3imgiVfqIRK4tAhUtnBoCF6rw_wcB Brian Brock's App Adventure - https://www.youtube.com/watch?v=HgNGJosQ6BE Touchstone.js (React Hybrid Apps)- http://touchstonejs.io/ Appguyver - http://www.appgyver.com/ Phonegap mobile accessibility - https://github.com/phonegap/phonegap-mobile-accessibility Article on modules in JavaScript - https://medium.com/@brianleroux/es6-modules-amd-and-commonjs-c1acefbe6fc0 Panelists Erik Isaksen - UX Engineer at3Pillar Global Danny Blue - Front End Engineer at Deloitte Digital Rachel Nabors - Web Animation Developer Advocate & Founder of TinMagpie

canada mobile native hybrid react adobe hailing javascript cordova crosswalk kony ionic cross platform mobile first web components firefox os phonegap ionic framework apache cordova kendo ui appcelerator

The Mobile Development Stack with Burke Holland

Play Episode Listen Later Apr 16, 2014 54:10

Carl and Richard talk to Burke Holland about building mobile apps. But the conversation starts out with an announcement - Telerik's KendoUI is going open source! Burke talks a bit about the history of KendoUI and how it has evolved over the years, including a KendoUI Mobile (which is also open source). That leads to a discussion about mobile development as a whole, including his preferred tools and styles for building apps across different mobile platforms, comparing native, hybrid and web development on the smartphone and where tablets fit into this story.Support this podcast at — https://redcircle.com/net-rocks/donations

microsoft studio visual vista burke stack orcas asp vb mobile development telerik kendo ui burke holland

The Mobile Development Stack with Burke Holland

Play Episode Listen Later Apr 16, 2014 54:09

Carl and Richard talk to Burke Holland about building mobile apps. But the conversation starts out with an announcement - Telerik's KendoUI is going open source! Burke talks a bit about the history of KendoUI and how it has evolved over the years, including a KendoUI Mobile (which is also open source). That leads to a discussion about mobile development as a whole, including his preferred tools and styles for building apps across different mobile platforms, comparing native, hybrid and web development on the smartphone and where tablets fit into this story.Support this podcast at — https://redcircle.com/net-rocks/donations

burke stack mobile development telerik kendo ui burke holland

Cross-Platform Mobile Development with Todd Anglin

microsoft studio visual vista orcas asp vb visual studio cross platform anglin mobile development telerik kendo ui

Play Episode Listen Later Oct 1, 2013 54:00

Carl and Richard talk to Todd Anglin from Telerik about cross-platform development for mobile. The conversation focuses on Telerik's Icenium hybrid mobile development solution. Todd announces that Icenium now has a Visual Studio plug-in so that you can do your development in the environment of your choice. This leads to interesting possibilities with KendoUI, another library from Telerik that lets you build mobile web apps with native look-and-feel on different phone platforms - now you can turn them into hybrid apps!Support this podcast at — https://redcircle.com/net-rocks/donations

Cross-Platform Mobile Development with Todd Anglin