POPULARITY
7 episodes with ngatlanta
6 episodes with ngatlanta
3 episodes with ngatlanta
8 episodes with ngatlanta
in this episode – facebook's React Fiber announcement – we go in a little about react vs angular and end up shouting out jquery – we talk about atlantas civic hack night that we'll be attending May 13 at the Garage. Shoutouts to @marktnoonan for hooking it up – we announce that we'll be the official interview partners for the ngAtlanta and nodeAtlanta conferences next feb. shoutouts to @ZChapple – we reveal our partnership we're working on called Render(ATL) and what we'll be doing with them – mehul spoils the battle of winterfell episode of game of thrones – we dont spoil endgame. that movie is great go watch it. – shoutouts the codeprep.io podcast – we do a lot of shoutouts. – shoutouts to shoutouts. – shoutouts to you. --- Send in a voice message: https://anchor.fm/peachtree-devs/message
--- Support this podcast: https://anchor.fm/angularair/support
Sponsors Sentry use the code "devchat" for $100 credit Angular Bootcamp TripleByte Panel Charles Max Wood John Papa Ward Bell Joined by Special Guests: Uri Shaked and Netta Bondi Episode Summary Netta is a senior web developer at a startup called Reali, although her degree is in social work. She also co-founded the largest community of women in research and Development in Israel. Netta and Uri are here to talk more about the talk they gave at FrontEnd Con about Angular Ivy and React Fiber. They share how this talk came to be. Uri and Netta compare Angular Ivy and React Fiber, which take different approaches to managing the cycle of code. The panel discusses whether or not there is an advantage to digging into the framework. Netta and Uri talk about some of the processes they explored while investigating Angular Ivy and React Fiber. They share techniques for not getting lost in the source code and delve into some of the differences between Angular Ivy and React Fiber. Through their investigations, they learned that the primary difference between the two is in the event delegation pattern. They advise that when deciding which technology to use, companies should consider which one will be easier to hire new employees for. The panel discusses whether or not big tree frameworks have become a commodity. Most new frameworks focus on making builds smaller and faster, but they would like new frameworks to have more benefits than just speed. The show is finished by Uri and Netta sharing how to track features down in Angular Ivy and React Fiber. Links Angular Ivy React Fiber Virtual DOM Incremental DOM Ajax jQuery Lin Clark - A Cartoon Intro to Fiber - React Conf 2017 Netta Bondy & Uri Shaked - React Fiber vs. Angular Ivy / FRONTEND CON 2018 Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Package Thief vs. Glitter Bomb Trap Help Charles move Devchat from WordPress to Eleventy and get an hour of coaching. Write show notes for 3 episodes and tag it, Charles will do an hour of coaching with you. John Papa: NG Atlanta Ward Bell: BlacKkKlansmen Uri Shaked: NG Atlanta Why We Sleep Uri is on Twitter as @UriShaked and github (urish) Netta Bondi: Hassan Minaj: Homecoming King Iliza Shlesinger: Elder Millennial Netta is on Medium and Twitter (@_bondit_)
Sponsors Sentry use the code "devchat" for $100 credit Angular Bootcamp TripleByte Panel Charles Max Wood John Papa Ward Bell Joined by Special Guests: Uri Shaked and Netta Bondi Episode Summary Netta is a senior web developer at a startup called Reali, although her degree is in social work. She also co-founded the largest community of women in research and Development in Israel. Netta and Uri are here to talk more about the talk they gave at FrontEnd Con about Angular Ivy and React Fiber. They share how this talk came to be. Uri and Netta compare Angular Ivy and React Fiber, which take different approaches to managing the cycle of code. The panel discusses whether or not there is an advantage to digging into the framework. Netta and Uri talk about some of the processes they explored while investigating Angular Ivy and React Fiber. They share techniques for not getting lost in the source code and delve into some of the differences between Angular Ivy and React Fiber. Through their investigations, they learned that the primary difference between the two is in the event delegation pattern. They advise that when deciding which technology to use, companies should consider which one will be easier to hire new employees for. The panel discusses whether or not big tree frameworks have become a commodity. Most new frameworks focus on making builds smaller and faster, but they would like new frameworks to have more benefits than just speed. The show is finished by Uri and Netta sharing how to track features down in Angular Ivy and React Fiber. Links Angular Ivy React Fiber Virtual DOM Incremental DOM Ajax jQuery Lin Clark - A Cartoon Intro to Fiber - React Conf 2017 Netta Bondy & Uri Shaked - React Fiber vs. Angular Ivy / FRONTEND CON 2018 Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Package Thief vs. Glitter Bomb Trap Help Charles move Devchat from WordPress to Eleventy and get an hour of coaching. Write show notes for 3 episodes and tag it, Charles will do an hour of coaching with you. John Papa: NG Atlanta Ward Bell: BlacKkKlansmen Uri Shaked: NG Atlanta Why We Sleep Uri is on Twitter as @UriShaked and github (urish) Netta Bondi: Hassan Minaj: Homecoming King Iliza Shlesinger: Elder Millennial Netta is on Medium and Twitter (@_bondit_)
Sponsors Sentry use the code "devchat" for $100 credit Angular Bootcamp TripleByte Panel Charles Max Wood John Papa Ward Bell Joined by Special Guests: Uri Shaked and Netta Bondi Episode Summary Netta is a senior web developer at a startup called Reali, although her degree is in social work. She also co-founded the largest community of women in research and Development in Israel. Netta and Uri are here to talk more about the talk they gave at FrontEnd Con about Angular Ivy and React Fiber. They share how this talk came to be. Uri and Netta compare Angular Ivy and React Fiber, which take different approaches to managing the cycle of code. The panel discusses whether or not there is an advantage to digging into the framework. Netta and Uri talk about some of the processes they explored while investigating Angular Ivy and React Fiber. They share techniques for not getting lost in the source code and delve into some of the differences between Angular Ivy and React Fiber. Through their investigations, they learned that the primary difference between the two is in the event delegation pattern. They advise that when deciding which technology to use, companies should consider which one will be easier to hire new employees for. The panel discusses whether or not big tree frameworks have become a commodity. Most new frameworks focus on making builds smaller and faster, but they would like new frameworks to have more benefits than just speed. The show is finished by Uri and Netta sharing how to track features down in Angular Ivy and React Fiber. Links Angular Ivy React Fiber Virtual DOM Incremental DOM Ajax jQuery Lin Clark - A Cartoon Intro to Fiber - React Conf 2017 Netta Bondy & Uri Shaked - React Fiber vs. Angular Ivy / FRONTEND CON 2018 Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Package Thief vs. Glitter Bomb Trap Help Charles move Devchat from WordPress to Eleventy and get an hour of coaching. Write show notes for 3 episodes and tag it, Charles will do an hour of coaching with you. John Papa: NG Atlanta Ward Bell: BlacKkKlansmen Uri Shaked: NG Atlanta Why We Sleep Uri is on Twitter as @UriShaked and github (urish) Netta Bondi: Hassan Minaj: Homecoming King Iliza Shlesinger: Elder Millennial Netta is on Medium and Twitter (@_bondit_)
Recording date: 2018-10-30 Tweet John Papa https://twitter.com/john_papa Ward Bell https://twitter.com/wardbell Dan Wahlin https://twitter.com/danwahlin Tracy Lee https://twitter.com/ladyleet Notes (0:01:00) Ward reads the mailbag https://twitter.com/plambweb/status/1057291112807723013 (0:01:35) Tracy says often the best answer to RxJS memory leaks is to check to unsubscribe (0:02:01) Tracy talks about RxJS in stencil https://stenciljs.com/, vue https://vuejs.org, react https://reactjs.org, angular https://angular.io, ionic https://ionicframework.com/ (0:03:12) Learn by making mistakes (0:03:50) Tracy talks about some places you can go wrong in RxJS (0:03:55) Introducing Tracy (0:04:20) Tracy's company https://www.thisdot.co/ (0:05:45) Tracy says she prefers frameworks for what they offer (0:06:10) Tracy talks about rxjs https://rxjs-dev.firebaseapp.com/ (0:06:30) Tracy mentions Ben Lesh and RxJS https://twitter.com/BenLesh (0:07:04) Tracy talks about reactive programming https://en.wikipedia.org/wiki/Reactive_programming as sets of events over time (0:07:47) TC39 https://www.ecma-international.org/memento/tc39-m.htm (0:08:00) Tracy explains how, generally, observables are stateless and lazy (0:08:50) Tracy discusses the stages of the TC39 (0:09:03) Babel https://babeljs.io/ (0:09:33) Ward asks what questions Tracy hears at her RxJS workshops https://www.thisdot.co/rx-workshop (0:10:03) Tracy says she hears a lot of confusion on observables and observers https://toddmotto.com/rxjs-observables-observers-operators (0:10:11) Tracy says rxjs operators can be a source of confusion https://www.learnrxjs.io/operators/ (0:10:55) Ben Lesh is working on RxJS 7 (0:11:15) Ward asks tracy how she slides people into rxjs easily (0:11:30) Tracy says she likes that Observables are just functions (0:12:54) John asks Tracy which operators in rxjs to learn first (0:13:53) Ward asks Tracy about the new RxJS docs (0:14:04) Ward talks about one of the creators of RxJS, Matt Podwysocki https://twitter.com/mattpodwysocki (0:14:20) Tracy talks about how RxJS was created as it is today from Netflix and Microsoft (0:15:02) Tracy says there are over 12 million downloads of rxjs a month (0:15:24) Ward mentions the RxJS docs https://rxjs-dev.firebaseapp.com/ (0:16:46) RxJS on npm https://www.npmjs.com/package/rxjs (0:17:50) John asks Tracy how she advises people on upgrade strategies for RxJS (0:18:45) Ward mentions the RxJS change from method chaining to pipe (0:18:49) Upgrade rxjs 5 to 6 https://www.learnrxjs.io/concepts/rxjs5-6.html (0:19:46) John asks Tracy what kind of applications she sees people creating with RxJS (0:20:00) Tracy talks about multi-plex over a websocket with rxjs with node.js and react native (0:20:22) Tracy mentions React Native https://facebook.github.io/react-native/ (0:20:37) Ken Wheeler https://twitter.com/ken_wheeler (0:21:28) Ward asks if "just subscribe" is a useful bit of advice (0:23:30) Tracy talks about reactive aspects and non reactive aspects of code (0:24:15) John mentions how RxJS is not part of any particular front end framework (0:24:30) Tracy says she is seeing a lot of React folks taking learning and using RxJS (0:24:34) Tracy talks about how RxJS is framework agnostic (0:25:17) Tracy talks about prtoecting from JavaScript fatigue (0:25:40) Ward asks Tracy how she recommends debugging RxJS (0:26:10) Tracy asys to "keep tapping away" (0:26:31) Tracy says they are trying to make testing easier (0:26:58) Tracy talks about how you can get into the RxJS slack channel (0:27:50) Tracy talks about her use of Evernote for staying organized (0:29:00) Tracy talks about her efforts with Women in Tech https://twitter.com/ladyleet/status/985018157994831872?lang=en (0:29:31) Tracy talks about possibly announcing something at the ngAtlanta: https://ng-atl.org/#/ conference (0:30:00) Tracy talks about her passion for creating companies (0:30:26) Someone to follow: Jay Phelps https://twitter.com/_jayphelps https://medium.com/@jayphelps (0:31:10) Someone to follow: Dmitri Shekhovtsov https://twitter.com/valorkin (0:31:50) Someone to follow: Dam Abramov https://twitter.com/dan_abramov Additional Resources RxJS api https://rxjs-dev.firebaseapp.com/api RxJS and Angular https://angular.io/guide/rx-library Upgrade RxJS 5 to 6 https://www.learnrxjs.io/concepts/rxjs5-6.html
Panel: Charles Max Wood Guest: Kim Crayton This week on My Angular Story, Charles speaks with Kim Crayton. Kim Crayton did a talk at NG Atlanta entitled “I Don’t Do Non-Technical Talks”. They talk about her passion behind this topic, as well as the importance of the human aspects of the job, failing in order to learn from your mistakes and the fact that programmers need to think about the long-term effects of their code. They also touch on core values and meeting people where they are. In particular, We dive pretty deep on: I Don’t Do Non-Technical Talks Critical thinking skills Need to be able to work with people The “human” skills are what matter in the job The human aspects in your job are what make or break your career #CauseAScene Has a Master’s degree in Training Development The importance of feedback from failure Change is the only thing that’s constant A lot of times, we look for the easy way to solve it Need to think of long-term effects of pushing code A business is a system “Soft” skills Understand the terms we are defining Agile development Need to look at the whole system Democratize business school education Teaching people how to build the business Look at core values Style guides Living documentation Meeting people where they are Get comfortable with being uncomfortable And much, much more! Links: I Don’t Do Non-Technical Talks Kim’s GitHub @KimCrayton1 KimCrayton.com Kim’s Medium
Panel: Charles Max Wood Guest: Kim Crayton This week on My Angular Story, Charles speaks with Kim Crayton. Kim Crayton did a talk at NG Atlanta entitled “I Don’t Do Non-Technical Talks”. They talk about her passion behind this topic, as well as the importance of the human aspects of the job, failing in order to learn from your mistakes and the fact that programmers need to think about the long-term effects of their code. They also touch on core values and meeting people where they are. In particular, We dive pretty deep on: I Don’t Do Non-Technical Talks Critical thinking skills Need to be able to work with people The “human” skills are what matter in the job The human aspects in your job are what make or break your career #CauseAScene Has a Master’s degree in Training Development The importance of feedback from failure Change is the only thing that’s constant A lot of times, we look for the easy way to solve it Need to think of long-term effects of pushing code A business is a system “Soft” skills Understand the terms we are defining Agile development Need to look at the whole system Democratize business school education Teaching people how to build the business Look at core values Style guides Living documentation Meeting people where they are Get comfortable with being uncomfortable And much, much more! Links: I Don’t Do Non-Technical Talks Kim’s GitHub @KimCrayton1 KimCrayton.com Kim’s Medium
Panel: Charles Max Wood Guest: Kim Crayton This week on My Angular Story, Charles speaks with Kim Crayton. Kim Crayton did a talk at NG Atlanta entitled “I Don’t Do Non-Technical Talks”. They talk about her passion behind this topic, as well as the importance of the human aspects of the job, failing in order to learn from your mistakes and the fact that programmers need to think about the long-term effects of their code. They also touch on core values and meeting people where they are. In particular, We dive pretty deep on: I Don’t Do Non-Technical Talks Critical thinking skills Need to be able to work with people The “human” skills are what matter in the job The human aspects in your job are what make or break your career #CauseAScene Has a Master’s degree in Training Development The importance of feedback from failure Change is the only thing that’s constant A lot of times, we look for the easy way to solve it Need to think of long-term effects of pushing code A business is a system “Soft” skills Understand the terms we are defining Agile development Need to look at the whole system Democratize business school education Teaching people how to build the business Look at core values Style guides Living documentation Meeting people where they are Get comfortable with being uncomfortable And much, much more! Links: I Don’t Do Non-Technical Talks Kim’s GitHub @KimCrayton1 KimCrayton.com Kim’s Medium
Panel: Charles Max Wood Alyssa Nicholl John Papa Joe Eames Special Guests: Shmuela Jacobs, Samantha Rhodes, and Bonnie Brennan In this episode of Adventures in Angular, the panel talks to Shmuela Jacobs, Samantha Rhodes, and Bonnie Brennan about ngGirls. ngGirls is an organization that provides a free one-day workshop with volunteer mentors who will teach them Angular basics. It was inspired by Django Girls and provides this type introduction to programming for women who want to learn about Angular. They are really passionate about bringing ngGirls all around the world so that women everywhere can be introduced to both Angular and programming. In particular, we dive pretty deep on: What is ngGirls? Started in November 2016 in Israel Django Girls Helps build motivation in young girls to keep programming Angular ngConf and Google I/O events coming up What is an ideal mentor? What does the curriculum look like? Angular Bootcamp Do you have a prep pack ahead of time? How do you sign up to be a mentor? Do you encourage people to organize their own ngGirls? How do you get the word out about the conferences? Using twitter How much experience do you need for ngGirls? They need more girls mentors Even if you’ve just started learning Angular, sign up as a mentor! And much, much more! Links: ngGirls ngAtlanta Django Girls Angular ngConf Google I/O Angular Bootcamp @AngularGirls @ShmuelaJ @Bonnster75 Bonnie ngConf Organizer @TheLittlestDev Sam’s Medium Picks: Charles Black Mirror Alyssa Ready Player One Movie Joe “Here are the best programming languages to learn in 2018” John ng-AI Hackathon by Microsoft Shmuela Arches National Park Angular in Depth Blog Octotree Sam ngConf Bonnie ngxs Dungeons and Dragons at ngConf Natasha Carlyon ngConf
Panel: Charles Max Wood Alyssa Nicholl John Papa Joe Eames Special Guests: Shmuela Jacobs, Samantha Rhodes, and Bonnie Brennan In this episode of Adventures in Angular, the panel talks to Shmuela Jacobs, Samantha Rhodes, and Bonnie Brennan about ngGirls. ngGirls is an organization that provides a free one-day workshop with volunteer mentors who will teach them Angular basics. It was inspired by Django Girls and provides this type introduction to programming for women who want to learn about Angular. They are really passionate about bringing ngGirls all around the world so that women everywhere can be introduced to both Angular and programming. In particular, we dive pretty deep on: What is ngGirls? Started in November 2016 in Israel Django Girls Helps build motivation in young girls to keep programming Angular ngConf and Google I/O events coming up What is an ideal mentor? What does the curriculum look like? Angular Bootcamp Do you have a prep pack ahead of time? How do you sign up to be a mentor? Do you encourage people to organize their own ngGirls? How do you get the word out about the conferences? Using twitter How much experience do you need for ngGirls? They need more girls mentors Even if you’ve just started learning Angular, sign up as a mentor! And much, much more! Links: ngGirls ngAtlanta Django Girls Angular ngConf Google I/O Angular Bootcamp @AngularGirls @ShmuelaJ @Bonnster75 Bonnie ngConf Organizer @TheLittlestDev Sam’s Medium Picks: Charles Black Mirror Alyssa Ready Player One Movie Joe “Here are the best programming languages to learn in 2018” John ng-AI Hackathon by Microsoft Shmuela Arches National Park Angular in Depth Blog Octotree Sam ngConf Bonnie ngxs Dungeons and Dragons at ngConf Natasha Carlyon ngConf
Panel: Charles Max Wood Alyssa Nicholl John Papa Joe Eames Special Guests: Shmuela Jacobs, Samantha Rhodes, and Bonnie Brennan In this episode of Adventures in Angular, the panel talks to Shmuela Jacobs, Samantha Rhodes, and Bonnie Brennan about ngGirls. ngGirls is an organization that provides a free one-day workshop with volunteer mentors who will teach them Angular basics. It was inspired by Django Girls and provides this type introduction to programming for women who want to learn about Angular. They are really passionate about bringing ngGirls all around the world so that women everywhere can be introduced to both Angular and programming. In particular, we dive pretty deep on: What is ngGirls? Started in November 2016 in Israel Django Girls Helps build motivation in young girls to keep programming Angular ngConf and Google I/O events coming up What is an ideal mentor? What does the curriculum look like? Angular Bootcamp Do you have a prep pack ahead of time? How do you sign up to be a mentor? Do you encourage people to organize their own ngGirls? How do you get the word out about the conferences? Using twitter How much experience do you need for ngGirls? They need more girls mentors Even if you’ve just started learning Angular, sign up as a mentor! And much, much more! Links: ngGirls ngAtlanta Django Girls Angular ngConf Google I/O Angular Bootcamp @AngularGirls @ShmuelaJ @Bonnster75 Bonnie ngConf Organizer @TheLittlestDev Sam’s Medium Picks: Charles Black Mirror Alyssa Ready Player One Movie Joe “Here are the best programming languages to learn in 2018” John ng-AI Hackathon by Microsoft Shmuela Arches National Park Angular in Depth Blog Octotree Sam ngConf Bonnie ngxs Dungeons and Dragons at ngConf Natasha Carlyon ngConf
0:15 We’re live! Chuck having technical difficulties. Discussion n progress with the Mental Toughness project. There is testing, testing, and more testing. EntreProgrammers talk about the marketing strategies for this new project, price testing and checking the number of sales. 5:00 Josh explains marketing tactics. John explains the promotion of the Bulldog mindset course along with the Mental Toughness project. Josh talk about the sells that took place during the promotion. 9:00 John explains more on the marketing analytics, conversion, and the emails sent to the list. John and Mani joke about the 9 dollar product price. Mani talks about creating a subset of the product. Josh talks about the product he can possibly sell, but the cheaper 5-9 dollar products will sell as a promotional tactic. 15:00 Mani, John, and Josh talk about Interview Cake. John mentions reading the Predictably Irrational book because of the interesting price setting topics. Josh mentioned that he is tapped out on writing promotions. Josh talks about strategies he has put out from John’s book. 24:00 Josh talks about a possible new course about how to get a job, and statics on interested and disinterested customers on promotions. Otherwise selling to a very small group which might not be worth the time. John asks about growing product sales after a long flatline. 30:00 Josh mention working with Podia, but needed to get some direction. Josh jokes about John being very knowledgeable about the numbers for someone who is not involved in the business anymore. Josh talks about having issues with permalinks. 37:00 Chuck talks about turning off caching on his podcast website because of a similar issue. Chuck talks about his recent trips to conferences and encountering bad rooms and bad internet. 40:00 Chuck talks about have done 20-30 recording at NG Atlanta for podcast purposes and youtube. Chuck shows the progress in his new PodWrench application and his plans on how this will eventually work with productions and placing sponsors. 47:00 Chuck explain how inviting and placing new sponsor will work. Mani asks about listenership, and download numbers. Mani asks a question about CPM and pricing and how the sponsor slots work. More talk on CPM. 56:00 Josh jokes about Baba, and how this new system is great for his business. Chuck talks about the evolving process with PodWrench and upcoming plans for the system. John and Josh say that PodWrench can be a great SAAS business soon. 1:00:00 Chuck talks about the different stages to move the application along. Chuck says PodWrench is not ready for the public, but it is getting there. Chuck talks about the different areas this sponsorship process can possibly fill for other podcasters. Chuck says this could turn him into a marketing agency for the podcast as this project grows. 1:05:00 Josh says this would be a great platform for marketing. Thoughts for the Week John - Just hang in there! Chuck - Take the breather Josh - Treat you affiliate like gold Mani - Understanding numbers
0:15 Chuck joke about his glare and Mani is in a detention room. Josh talks about his wireless 8lb headset. The EntreProgrammers talk about the wireless headphones and the troubles with the AirPods. John jokes that Josh electronic trouble because he is like Powder. 5:00 Mani talks about his recent price increase with his product and research on keywords for branding proposes. Mani talks about change or rebranding based on Confidence and Mental Toughness keywords. John gives feedback on a book What Doesn’t Kill Us. 9:00 John talks about doing an AB test on the titles to see what does better. Josh suggest base on YouTube content. Chuck talks about long tail searches base on titles and words. Mani talks about the issues with titling Mental Toughness and Self Confidence. Mani asks John what he would like to use as a title, Mental Toughness. Josh, John, and Mani plan their attack with the upcoming product. 15:00 John talks about doing an interview with the founder of Quest Nutrition, Tom Bilyeu. John talks about Tom’s Youtube channel, Impact Theory. John and Mani talk about the net worth of the company and other details. John talks about trying to get Tye Lopez on the show… 20:00 John talks about the myth of Facebook advertising. John says show him a profitable Facebook ad. The EntreProgarmmer talk about finding someone who has profitable Facebook Ads. Josh talks about selling low price products verse high price product on platforms like Facebook. 25:00 The EntreProgrammer talk about webinars and facebook marketing. Also some talk about paid traffic. John talks about what profitable Facebook ads should look like. 30:00 Josh talks about the blog update in Simple Programmer. Looks like the numbers have increased and ranking boost. Josh talks about the traffic on their blog posts and the guest posting numbers. Mani ask a question about posts from 2016. John talks about guests post and numbers reached last year. 35:00 John talks about pruning some posts to increase the numbers. Chuck talks about his visit at NG Atlanta. Chuck talks about doing an interview on Youtube and podcasts. Chuck talks about how is camera does not have an audio input. Mani suggests recording the video with a phone and having audio hookups. 40:00 Chuck says his Social Media person quit. Also, some work with Dropbox cleanup and moving files around to get organized. Josh chimes back in with numbers from last years traffic. Josh talks about the editorial team for the blog posts. 45:00 Josh talk about testing out the articles. Josh talks about doing keyword optimization and backlinking. John talks about the strategy with backlinks and getting some coaching on the topic. 53:00 Chuck talks about getting some big name for the first episode of the Vue Podcast Thoughts of the Week! John - Make sure you remind yourself of things that nullify your goals Josh - Believe there is a solution! Chuck - Building Systems! Mani - Understanding the customer journey!
Panel: Ward Bell Joe Eames Charles Max Wood Special Guests: Zack Chapple & Kim Maida In the episode of Adventures in Angular the panel speaks with Zack Chapple. Zack is a software architect at Career Builder , and is the founder and main organizer for NG Atlanta. Zack is on the show to talks about the inspiration for NG Atlanta and the origin stories of the conference. Zack describes the details and goals of the conferences concerning diversity, demographics, and technology. Also joining the show is Kim Maida. Kim is the technical content lead at Auth0. Kim talks about the demographics of women and the diversity of the conference speaks and attendees. Zack is on the show to talks about the inspiration for NG Atlanta and the origin stories of the conference. Zack describes the details and goals of the conferences concerning diversity, demographics, and technology. In particular, we dive pretty deep on: NG Atlanta - Two-day workshop and Two single-track conference Diversity, Inclusion, Angular Technology related to Angular Leverage where we are in technology Origin story of NG Atlanta Programs Holistic approach Community and interpersonal skills Diversity 50 percent of speakers are women Tech conferences and statistics Contributions Diversity and Demographics Calling out conferences Putting together conferences Code of conduct Criteria for conferences and much more! Links: https://www.careerbuilder.com http://ng-atl.org @KimMaida @zchapple https://auth0.com/blog/ Picks: Charles Star Wars Indiegogo for View and React, and Elixir Joe Murder on the Orient Express Ward Translation of the Odyssey Zach Vets Who Code Bright Kim NG Girls Deep Space 9
Panel: Ward Bell Joe Eames Charles Max Wood Special Guests: Zack Chapple & Kim Maida In the episode of Adventures in Angular the panel speaks with Zack Chapple. Zack is a software architect at Career Builder , and is the founder and main organizer for NG Atlanta. Zack is on the show to talks about the inspiration for NG Atlanta and the origin stories of the conference. Zack describes the details and goals of the conferences concerning diversity, demographics, and technology. Also joining the show is Kim Maida. Kim is the technical content lead at Auth0. Kim talks about the demographics of women and the diversity of the conference speaks and attendees. Zack is on the show to talks about the inspiration for NG Atlanta and the origin stories of the conference. Zack describes the details and goals of the conferences concerning diversity, demographics, and technology. In particular, we dive pretty deep on: NG Atlanta - Two-day workshop and Two single-track conference Diversity, Inclusion, Angular Technology related to Angular Leverage where we are in technology Origin story of NG Atlanta Programs Holistic approach Community and interpersonal skills Diversity 50 percent of speakers are women Tech conferences and statistics Contributions Diversity and Demographics Calling out conferences Putting together conferences Code of conduct Criteria for conferences and much more! Links: https://www.careerbuilder.com http://ng-atl.org @KimMaida @zchapple https://auth0.com/blog/ Picks: Charles Star Wars Indiegogo for View and React, and Elixir Joe Murder on the Orient Express Ward Translation of the Odyssey Zach Vets Who Code Bright Kim NG Girls Deep Space 9
Panel: Ward Bell Joe Eames Charles Max Wood Special Guests: Zack Chapple & Kim Maida In the episode of Adventures in Angular the panel speaks with Zack Chapple. Zack is a software architect at Career Builder , and is the founder and main organizer for NG Atlanta. Zack is on the show to talks about the inspiration for NG Atlanta and the origin stories of the conference. Zack describes the details and goals of the conferences concerning diversity, demographics, and technology. Also joining the show is Kim Maida. Kim is the technical content lead at Auth0. Kim talks about the demographics of women and the diversity of the conference speaks and attendees. Zack is on the show to talks about the inspiration for NG Atlanta and the origin stories of the conference. Zack describes the details and goals of the conferences concerning diversity, demographics, and technology. In particular, we dive pretty deep on: NG Atlanta - Two-day workshop and Two single-track conference Diversity, Inclusion, Angular Technology related to Angular Leverage where we are in technology Origin story of NG Atlanta Programs Holistic approach Community and interpersonal skills Diversity 50 percent of speakers are women Tech conferences and statistics Contributions Diversity and Demographics Calling out conferences Putting together conferences Code of conduct Criteria for conferences and much more! Links: https://www.careerbuilder.com http://ng-atl.org @KimMaida @zchapple https://auth0.com/blog/ Picks: Charles Star Wars Indiegogo for View and React, and Elixir Joe Murder on the Orient Express Ward Translation of the Odyssey Zach Vets Who Code Bright Kim NG Girls Deep Space 9
Panel: Ward Bell Alyssa Nicoll Joe Eames John Charles Max Wood Special Guests: Jesse Sanders In the episode of Adventures in Angular the panel speaks with Jesse Sanders. Jesse is the CEO of BrieBug, A consulting firm in Denver Colorado. Jesse talks about the interesting challenges his company encounters with helping their clients with form creative solutions. Jesse mentions being a developer for over 20 years and familiarity with many platforms. Jesse is on the show to talk about NGRZX, Entities, Redux States, etc, the panel asks questions about how this all applies to Angular. Jesse talks about the current complexities and how these tools handle events, components, etc. This is a great episode to learn more about NGRX, Entities, and Redux, and how they used with Angular. In particular, we dive pretty deep on: •What does BrieBug do for its clients? Show what is the state management stuff? Thousand lines of code? Dumb and Smart components Redux? Isn’t that a React Thingy Redux is just a pattern Un-opinionated Nested data Mabex Redux has much ceremony around it… Choosing redux Shared State There is no one sire fits all solution If NGRX was right for us? Combining states Normalizing data first Converting data from ray data Using an adapter Dictionaries Deconstructing How to we make its NGRX pattern easier? Difficulties with the patterns Learning the step zone •and much more! Links: https://www.briebug.com https://github.com/briebug https://www.youtube.com/watch?v=pffEkpuZpPo Slides from presentation Picks: Charles NG Atlanta Indiegogo for View and React, and Elixir Echo John Learning more about View, React, and Angular Ward Going to see Star Wars Joe NG Conf. BrieBug.com Jesse Sanders Heroku Alyssa Survey Results for the state of JavaScript Jesse NG Dock io Star Wars Jes JS
Panel: Ward Bell Alyssa Nicoll Joe Eames John Charles Max Wood Special Guests: Jesse Sanders In the episode of Adventures in Angular the panel speaks with Jesse Sanders. Jesse is the CEO of BrieBug, A consulting firm in Denver Colorado. Jesse talks about the interesting challenges his company encounters with helping their clients with form creative solutions. Jesse mentions being a developer for over 20 years and familiarity with many platforms. Jesse is on the show to talk about NGRZX, Entities, Redux States, etc, the panel asks questions about how this all applies to Angular. Jesse talks about the current complexities and how these tools handle events, components, etc. This is a great episode to learn more about NGRX, Entities, and Redux, and how they used with Angular. In particular, we dive pretty deep on: •What does BrieBug do for its clients? Show what is the state management stuff? Thousand lines of code? Dumb and Smart components Redux? Isn’t that a React Thingy Redux is just a pattern Un-opinionated Nested data Mabex Redux has much ceremony around it… Choosing redux Shared State There is no one sire fits all solution If NGRX was right for us? Combining states Normalizing data first Converting data from ray data Using an adapter Dictionaries Deconstructing How to we make its NGRX pattern easier? Difficulties with the patterns Learning the step zone •and much more! Links: https://www.briebug.com https://github.com/briebug https://www.youtube.com/watch?v=pffEkpuZpPo Slides from presentation Picks: Charles NG Atlanta Indiegogo for View and React, and Elixir Echo John Learning more about View, React, and Angular Ward Going to see Star Wars Joe NG Conf. BrieBug.com Jesse Sanders Heroku Alyssa Survey Results for the state of JavaScript Jesse NG Dock io Star Wars Jes JS
Panel: Ward Bell Alyssa Nicoll Joe Eames John Charles Max Wood Special Guests: Jesse Sanders In the episode of Adventures in Angular the panel speaks with Jesse Sanders. Jesse is the CEO of BrieBug, A consulting firm in Denver Colorado. Jesse talks about the interesting challenges his company encounters with helping their clients with form creative solutions. Jesse mentions being a developer for over 20 years and familiarity with many platforms. Jesse is on the show to talk about NGRZX, Entities, Redux States, etc, the panel asks questions about how this all applies to Angular. Jesse talks about the current complexities and how these tools handle events, components, etc. This is a great episode to learn more about NGRX, Entities, and Redux, and how they used with Angular. In particular, we dive pretty deep on: •What does BrieBug do for its clients? Show what is the state management stuff? Thousand lines of code? Dumb and Smart components Redux? Isn’t that a React Thingy Redux is just a pattern Un-opinionated Nested data Mabex Redux has much ceremony around it… Choosing redux Shared State There is no one sire fits all solution If NGRX was right for us? Combining states Normalizing data first Converting data from ray data Using an adapter Dictionaries Deconstructing How to we make its NGRX pattern easier? Difficulties with the patterns Learning the step zone •and much more! Links: https://www.briebug.com https://github.com/briebug https://www.youtube.com/watch?v=pffEkpuZpPo Slides from presentation Picks: Charles NG Atlanta Indiegogo for View and React, and Elixir Echo John Learning more about View, React, and Angular Ward Going to see Star Wars Joe NG Conf. BrieBug.com Jesse Sanders Heroku Alyssa Survey Results for the state of JavaScript Jesse NG Dock io Star Wars Jes JS
0:15 We’re are alive! EntreProgrammers joke about ending on episode 199 with some cliffhangers. EntreProgarmmers talk about BS TV show endings that suck. 3:30 John mentions hiring a new SEO person and soon a writer to join Simple Programmer. Josh talks but some new on search formats on Google mobile. Josh says this is a tactic from Google to only click on Google Ads, rather than clicking through to actual sites. 8:00 Josh talks about, what if ISPs charges to be on YouTube. Thinning of the herd or channels. John says you need to be willing to take the anit-fragile approach and adapted to the changes. 11:00 Chuck talks about government or FCC control of the internet. John talks about how monopolies work when you are a billionaire. EntreProgarmmers discuss government control of the internet and the talk about net neutrality. John further gives his thought on new neutrality and herd mentality. 22:00 Josh mentions a death threat at Simple Programmer. But, generally a great month for product sales and launches. John and Josh talk about the book sales and finally seeing the revenue this month. John mentions reading the book Profit First. John mentions that they already have been taking profits first in Simple Programmer. 28:00 Josh talks about taking a budget amount for themselves for business expenses and payroll. John asks, where can we put our money to grow the revenue since expenses are low at the time. John talks about growing the company to the point where your hires are hiring people. 32:00 Johns said that were trying to launch the audiobook next week, but it looks unlikely. Audible has some other plans to review the book before it is published. EntreProgrammers discuss the Kindle and Audible books and how to choose to publish. 36:00 Chuck talks about being sick and not being able to send out important emails. Also, some talks about getting support on Patreon for some new launches conference and podcasts. 38:00 Chuck talks about possibly selling The Freelancer’s Show. Chuck mentions the new features on Podwrench and the slick automation functions. Chuck talks about hiring Michelle, to help with booking podcasts guest for the shows. Also a new hire for social media stuff. 42:00 Chuck mention moving to the app called Convo, instead of Slack. Chuck also mentions doing some work for growing the podcast business. Chuck mentions that Linode also renewed for the rest of the year. 46:00 Chuck talks about reaching the NG Atlanta and Angular conference to do some interview for Angular podcasts. Chuck talks about his plans do interview at conferences and do networking in the next year. 53:00 Chuck talks about learning about the Netty Pot and cleaning out sinus. Chuck talks about plugging away to find great hires. Looking for people who don’t need to be managed Thoughts of the Week Chuck - It hurts to move up to the top. Josh - Trying to help people remove barriers. John - Project forward 5 years a decision. No matter what you do, you’re going to get burned. So you might as well make a decision, rather do nothing.
Panel: Joe Eames Alyssa Nicoll Charles Max Wood Ward Bell Aaron Frost In the episode of Adventures in Angular, the panel’s discussion topic is about upgrading Angular. The panel covers preparation and the difficulties of getting started with the upgrade service. Notably, basic users do not understand the process of the updated with simple applications. Also, playing with the idea to rewrite your applications in Angular directly, or do we just upgrade? In particular, we dive pretty deep on: NG upgrading - preparation with a module loader. It is a mess to get started Look at you Angular JSJ, and ask what am I gaining by doing this? Can you write it in a different Angular directly? How long till am I off of Angular JS or Backbone? Application is written in Angular JS Legacy documentation for updates Annotating and bundling Angular solves the performance stuff Having someone in charge of it will have a smooth transition Convenient function with upgrading Upgrading big applications vs. Rewriting. Typescript Migration Upgrading components and much more! Links: NG Conf. 2018 Picks: Ward NG Atlanta Neutron Star Collision Alyssa NG Atlanta Joe Migrations NG CONF. Aaron Neutron Star Collision
Panel: Joe Eames Alyssa Nicoll Charles Max Wood Ward Bell Aaron Frost In the episode of Adventures in Angular, the panel’s discussion topic is about upgrading Angular. The panel covers preparation and the difficulties of getting started with the upgrade service. Notably, basic users do not understand the process of the updated with simple applications. Also, playing with the idea to rewrite your applications in Angular directly, or do we just upgrade? In particular, we dive pretty deep on: NG upgrading - preparation with a module loader. It is a mess to get started Look at you Angular JSJ, and ask what am I gaining by doing this? Can you write it in a different Angular directly? How long till am I off of Angular JS or Backbone? Application is written in Angular JS Legacy documentation for updates Annotating and bundling Angular solves the performance stuff Having someone in charge of it will have a smooth transition Convenient function with upgrading Upgrading big applications vs. Rewriting. Typescript Migration Upgrading components and much more! Links: NG Conf. 2018 Picks: Ward NG Atlanta Neutron Star Collision Alyssa NG Atlanta Joe Migrations NG CONF. Aaron Neutron Star Collision
Panel: Joe Eames Alyssa Nicoll Charles Max Wood Ward Bell Aaron Frost In the episode of Adventures in Angular, the panel’s discussion topic is about upgrading Angular. The panel covers preparation and the difficulties of getting started with the upgrade service. Notably, basic users do not understand the process of the updated with simple applications. Also, playing with the idea to rewrite your applications in Angular directly, or do we just upgrade? In particular, we dive pretty deep on: NG upgrading - preparation with a module loader. It is a mess to get started Look at you Angular JSJ, and ask what am I gaining by doing this? Can you write it in a different Angular directly? How long till am I off of Angular JS or Backbone? Application is written in Angular JS Legacy documentation for updates Annotating and bundling Angular solves the performance stuff Having someone in charge of it will have a smooth transition Convenient function with upgrading Upgrading big applications vs. Rewriting. Typescript Migration Upgrading components and much more! Links: NG Conf. 2018 Picks: Ward NG Atlanta Neutron Star Collision Alyssa NG Atlanta Joe Migrations NG CONF. Aaron Neutron Star Collision
Panel: Joe Eames Alyssa Nicoll Charles Max Wood Ward Bell Special Guests: Aaron Frost In the episode of Adventures in Angular, the panel speaks with Aaron Frost. Aaron is a return guest and works at SaltStack. In this episode, the panel and Aaron ask questions about the upcoming NG Conf. 2018. The panel discusses the many exciting upcoming topics discussions, events, and speakers. Importantly, Aaron and Joe give a preview of the theme of the event. Aaron mentions, for this year, NG Conf. is going to be about what the community wants to hear about. This is based on recent surveys taken by developers and new coders. These particular details extend into to specific speakers and the level of expertise for discussion. In particular, we dive pretty deep on: •NG Conf. - Grand America - April 18-20, 2018 Kid Conference 2 whole days of workshops Same intro as last year Schedule of workshops and event speakers Parties and food Activities Theme - around “Ready Player One” - 80s Who is coming and who is speaking Number 1 thing to come away with - NGRX #3 - Actually Animation? Non-Angular topics? AI, Electro. Ticket Sales - Waitlist raffle, •and much more! Links: •SaltStack •NG Conf. 2018 •github.com/aaronfrost/ama •github/bryanforbes •Grand America Booking Ready Player One Picks: Ward •Backpacking Alyssa •NG Atlanta Joe •Steve Harvey - Jump One Man Star Wars Trilogy Charles •The Banished of Muirwood Just code Aaron •Can’t Make This Stuff Up •White Velvet Cake Prayers for all recent disaster
Panel: Joe Eames Alyssa Nicoll Charles Max Wood Ward Bell Special Guests: Aaron Frost In the episode of Adventures in Angular, the panel speaks with Aaron Frost. Aaron is a return guest and works at SaltStack. In this episode, the panel and Aaron ask questions about the upcoming NG Conf. 2018. The panel discusses the many exciting upcoming topics discussions, events, and speakers. Importantly, Aaron and Joe give a preview of the theme of the event. Aaron mentions, for this year, NG Conf. is going to be about what the community wants to hear about. This is based on recent surveys taken by developers and new coders. These particular details extend into to specific speakers and the level of expertise for discussion. In particular, we dive pretty deep on: •NG Conf. - Grand America - April 18-20, 2018 Kid Conference 2 whole days of workshops Same intro as last year Schedule of workshops and event speakers Parties and food Activities Theme - around “Ready Player One” - 80s Who is coming and who is speaking Number 1 thing to come away with - NGRX #3 - Actually Animation? Non-Angular topics? AI, Electro. Ticket Sales - Waitlist raffle, •and much more! Links: •SaltStack •NG Conf. 2018 •github.com/aaronfrost/ama •github/bryanforbes •Grand America Booking Ready Player One Picks: Ward •Backpacking Alyssa •NG Atlanta Joe •Steve Harvey - Jump One Man Star Wars Trilogy Charles •The Banished of Muirwood Just code Aaron •Can’t Make This Stuff Up •White Velvet Cake Prayers for all recent disaster
Panel: Joe Eames Alyssa Nicoll Charles Max Wood Ward Bell Special Guests: Aaron Frost In the episode of Adventures in Angular, the panel speaks with Aaron Frost. Aaron is a return guest and works at SaltStack. In this episode, the panel and Aaron ask questions about the upcoming NG Conf. 2018. The panel discusses the many exciting upcoming topics discussions, events, and speakers. Importantly, Aaron and Joe give a preview of the theme of the event. Aaron mentions, for this year, NG Conf. is going to be about what the community wants to hear about. This is based on recent surveys taken by developers and new coders. These particular details extend into to specific speakers and the level of expertise for discussion. In particular, we dive pretty deep on: •NG Conf. - Grand America - April 18-20, 2018 Kid Conference 2 whole days of workshops Same intro as last year Schedule of workshops and event speakers Parties and food Activities Theme - around “Ready Player One” - 80s Who is coming and who is speaking Number 1 thing to come away with - NGRX #3 - Actually Animation? Non-Angular topics? AI, Electro. Ticket Sales - Waitlist raffle, •and much more! Links: •SaltStack •NG Conf. 2018 •github.com/aaronfrost/ama •github/bryanforbes •Grand America Booking Ready Player One Picks: Ward •Backpacking Alyssa •NG Atlanta Joe •Steve Harvey - Jump One Man Star Wars Trilogy Charles •The Banished of Muirwood Just code Aaron •Can’t Make This Stuff Up •White Velvet Cake Prayers for all recent disaster
JSJ 269 Reusable React and JavaScript Components with Cory House On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in! [00:01:35] – Overview We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done. Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. [00:04:50] – Browser support issue The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components. Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead. [00:07:50] – Polymer The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser. [00:14:20] – Standards are dead No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library. Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about. [00:17:05] – Libraries making reusable components There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well. As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there [00:21:20] – Why opt for reusable components Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse. As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components. [00:31:20] – Rigid component vs. flexible component As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder. We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough. Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later. [00:36:00] – Reusable components The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously. We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue. [00:42:45] – Component development on teams Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need. [00:47:45] – Mobile to web crossover Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application. [00:50:00] – Challenge Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?" Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember. Picks Cory House Creating Reusable React Components on Pluralsight Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss Joe Eames UI-Router Persistence Aimee Knight Ask HN: People who completed a boot camp 3+ years ago, what are you doing now? NgAtlanta Charles Max Wood Upwork.com JSJ 269 Reusable React and JavaScript Components with Cory House On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in! [00:01:35] – Overview We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done. Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. [00:04:50] – Browser support issue The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components. Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead. [00:07:50] – Polymer The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser. [00:14:20] – Standards are dead No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library. Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about. [00:17:05] – Libraries making reusable components There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well. As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there [00:21:20] – Why opt for reusable components Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse. As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components. [00:31:20] – Rigid component vs. flexible component As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder. We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough. Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later. [00:36:00] – Reusable components The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously. We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue. [00:42:45] – Component development on teams Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need. [00:47:45] – Mobile to web crossover Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application. [00:50:00] – Challenge Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?" Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember. Picks Cory House Creating Reusable React Components on Pluralsight Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss Joe Eames UI-Router Persistence Aimee Knight Ask HN: People who completed a boot camp 3+ years ago, what are you doing now? NgAtlanta Charles Max Wood Upwork.com
JSJ 269 Reusable React and JavaScript Components with Cory House On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in! [00:01:35] – Overview We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done. Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. [00:04:50] – Browser support issue The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components. Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead. [00:07:50] – Polymer The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser. [00:14:20] – Standards are dead No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library. Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about. [00:17:05] – Libraries making reusable components There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well. As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there [00:21:20] – Why opt for reusable components Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse. As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components. [00:31:20] – Rigid component vs. flexible component As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder. We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough. Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later. [00:36:00] – Reusable components The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously. We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue. [00:42:45] – Component development on teams Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need. [00:47:45] – Mobile to web crossover Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application. [00:50:00] – Challenge Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?" Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember. Picks Cory House Creating Reusable React Components on Pluralsight Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss Joe Eames UI-Router Persistence Aimee Knight Ask HN: People who completed a boot camp 3+ years ago, what are you doing now? NgAtlanta Charles Max Wood Upwork.com JSJ 269 Reusable React and JavaScript Components with Cory House On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in! [00:01:35] – Overview We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done. Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. [00:04:50] – Browser support issue The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components. Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead. [00:07:50] – Polymer The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser. [00:14:20] – Standards are dead No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library. Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about. [00:17:05] – Libraries making reusable components There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well. As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there [00:21:20] – Why opt for reusable components Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse. As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components. [00:31:20] – Rigid component vs. flexible component As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder. We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough. Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later. [00:36:00] – Reusable components The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously. We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue. [00:42:45] – Component development on teams Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need. [00:47:45] – Mobile to web crossover Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application. [00:50:00] – Challenge Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?" Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember. Picks Cory House Creating Reusable React Components on Pluralsight Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss Joe Eames UI-Router Persistence Aimee Knight Ask HN: People who completed a boot camp 3+ years ago, what are you doing now? NgAtlanta Charles Max Wood Upwork.com
JSJ 269 Reusable React and JavaScript Components with Cory House On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in! [00:01:35] – Overview We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done. Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. [00:04:50] – Browser support issue The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components. Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead. [00:07:50] – Polymer The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser. [00:14:20] – Standards are dead No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library. Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about. [00:17:05] – Libraries making reusable components There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well. As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there [00:21:20] – Why opt for reusable components Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse. As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components. [00:31:20] – Rigid component vs. flexible component As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder. We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough. Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later. [00:36:00] – Reusable components The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously. We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue. [00:42:45] – Component development on teams Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need. [00:47:45] – Mobile to web crossover Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application. [00:50:00] – Challenge Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?" Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember. Picks Cory House Creating Reusable React Components on Pluralsight Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss Joe Eames UI-Router Persistence Aimee Knight Ask HN: People who completed a boot camp 3+ years ago, what are you doing now? NgAtlanta Charles Max Wood Upwork.com JSJ 269 Reusable React and JavaScript Components with Cory House On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in! [00:01:35] – Overview We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done. Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. [00:04:50] – Browser support issue The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components. Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead. [00:07:50] – Polymer The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser. [00:14:20] – Standards are dead No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library. Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about. [00:17:05] – Libraries making reusable components There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well. As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there [00:21:20] – Why opt for reusable components Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse. As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components. [00:31:20] – Rigid component vs. flexible component As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder. We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough. Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later. [00:36:00] – Reusable components The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously. We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue. [00:42:45] – Component development on teams Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need. [00:47:45] – Mobile to web crossover Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application. [00:50:00] – Challenge Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?" Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember. Picks Cory House Creating Reusable React Components on Pluralsight Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss Joe Eames UI-Router Persistence Aimee Knight Ask HN: People who completed a boot camp 3+ years ago, what are you doing now? NgAtlanta Charles Max Wood Upwork.com
© 2020-2025 Ivy Podcast Discovery LLC
