Podcasts about angular boot camp

Let's be honest, most engineers are not good designers. Working closely with product and design teams improves our applications, and is necessary for building a successful product. So, what are design systems and what role do they play to solve this challenge?In this episode of the Angular Show, we sit down with our friend Bill Odom. Bill loves Angular and his passion is to share his knowledge with the community, through speaking and teaching. Bill is a trainer at Oasis Digital that provides the popular Angular Bootcamp training. The panelists learn from Bill that design systems enable effective communication, planning, implementation, and ongoing maintenance of user interface and experience between engineering, design, and product development teams.You can expect to learn what a design system is, how they are valuable to organizations, some widely used design systems today, integrating design systems with tooling to develop components in isolation such as Storybook, and how design tokens fit into the model. Angular is well-positioned for developing applications using modern tooling, including design tokens, design systems, and more. Don't forget to subscribe so you can follow along with the panelists as they learn from community members like Bill.Show Notes:Oasis Digitalhttps://oasisdigital.com/https://oasisdigital.com/traininghttps://oasisdigital.com/code-talk-teach/Angular and CSS Grid: Get ready to fall in love - ng-conf 2019 - https://youtu.be/lh6n0JxXD_gStorybookhttps://storybook.js.org/Angular and Storybook, Oasis Digital - Nathan Kerr - https://www.2021.ng-conf.org/workshops/angular-and-storybook,-oasis-digitalThe benefits of a design system - Angular Berlin - Kai Röder - https://youtu.be/mWsNQB0fV38Design tokensWTF are Design Tokens? - Jina Anne - https://youtu.be/q5qIowMyVt8Theo - SalesForce - https://github.com/salesforce-ux/theoStyle Dictionary - Amazon - https://amzn.github.io/style-dictionary/Why Angular is the best framework for a design system - Jan Greger Hemb -https://youtu.be/yERBKsNVE60Connect with us:Brian F Love - @brian_loveAaron Frost - @aaronfrostJennifer Wadella - @likeOMGitsFEDAYBill Odom - @wnodom

In this episode of Adventures in Angular the panel has fun interviewing David East about Firebase. David starts by sharing what it was like at the recent Firebase Summit in Madrid. There were so many announcements they had a tough time fitting them all into the one-hour keynote address.    One of the cool new features announced at the Firebase Summit is Firebase Extension, David describes it as serverless without any code. The panel discusses this feature and how it works. Another cool feature announced is Google Analytics for Firebase. This allows you to use Firebase tools in conjunction with Google Analytics. The panel considers the smart things you can do in your app with this feature.    The next feature the panel discusses is Remote Config which allows you to store data and then pull out that information on demand. If you use the Google Analytics for Firebase you can target specific data for certain audiences. David explains that before this could only be done with native apps. He also explains how in doing this you no longer have to worry about the gtag loader and defines gtag for the panel.    The panel gets a little off track as David jokingly explains his beef with Aaron Frost, Frosty. Frosty host My Angular Story and a while back had twitted looking for awesome angular stories. David had responded but never heard back from Frosty. Frosty jokingly says he faxed an invite to David. The panel jokes about how awesome David’s episode will be and tells everyone to look out for his episode.    Getting back on track, David gives more examples of ways to use the Remote Config feature on with the Google Analytics for Firebase. Frosty confesses he needs to get better at looking at analytics. Sharing an example from a company he is currently working for, Frosty explains how they made nearly 2 million dollars just by changing the color of a button. The panel considers how minor changes like that can make such a big difference and how analytics helps you target your audience.    David shares the story behind writing Angular Fire. Jeff Cross worked on the angular team and started writing angular fire but then left for Nrwl. After Jeff left, David took over and ended up rewriting the entire library. He explains some of the mistakes that they made that led to the rewrite and how he fixed them.    The panel wonders at David about using Angular Fire and NgRX. David tells the panel that the Firebase console uses NgRx under the hood and shares what he learned while working on it. Using firebase and NgRx can be very confusing because of the mass duplication of responsibility. David’s advice is to let Firebase and NgRx do their own thing and connect the dots with RxJs.    David discusses Firestore, a very advanced caching system and what you can do with it. Including, working offline and setting security rules. Frosty brings up Firebase Messaging Cues, he explains that it is similar to three-way messaging cues except its n-way. David explains that even though he is intrigued by the idea, he does not approve of the name. The panel considers possible use cases for an n-way messaging cue. David explains some of the costs and benefits of this architecture.    The episode ends with a discussion of Firebase’s documentation, which is currently a group of markdown files. David defends the simplicity of this documentation style and gives recommendations and resources for those who need more help.  Panelists Aaron Frost Brian Love Alyssa Nicoll Shai Reznik Guest David East Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://firebase.google.com/ https://firebase.google.com/summit My Angular Story https://fireship.io/ Fireship Youtube https://twitter.com/_davideast https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: Bonnie Love Aaron Frost: Stop shaming people Miss Saigon Alyssa Nicoll: David East David East: Alyssa Nicoll Freakonomics The Signal and the Noise: Why So Many Predictions Fail-But Some Don't  

In this episode of Adventures in Angular the panel has fun interviewing David East about Firebase. David starts by sharing what it was like at the recent Firebase Summit in Madrid. There were so many announcements they had a tough time fitting them all into the one-hour keynote address.    One of the cool new features announced at the Firebase Summit is Firebase Extension, David describes it as serverless without any code. The panel discusses this feature and how it works. Another cool feature announced is Google Analytics for Firebase. This allows you to use Firebase tools in conjunction with Google Analytics. The panel considers the smart things you can do in your app with this feature.    The next feature the panel discusses is Remote Config which allows you to store data and then pull out that information on demand. If you use the Google Analytics for Firebase you can target specific data for certain audiences. David explains that before this could only be done with native apps. He also explains how in doing this you no longer have to worry about the gtag loader and defines gtag for the panel.    The panel gets a little off track as David jokingly explains his beef with Aaron Frost, Frosty. Frosty host My Angular Story and a while back had twitted looking for awesome angular stories. David had responded but never heard back from Frosty. Frosty jokingly says he faxed an invite to David. The panel jokes about how awesome David’s episode will be and tells everyone to look out for his episode.    Getting back on track, David gives more examples of ways to use the Remote Config feature on with the Google Analytics for Firebase. Frosty confesses he needs to get better at looking at analytics. Sharing an example from a company he is currently working for, Frosty explains how they made nearly 2 million dollars just by changing the color of a button. The panel considers how minor changes like that can make such a big difference and how analytics helps you target your audience.    David shares the story behind writing Angular Fire. Jeff Cross worked on the angular team and started writing angular fire but then left for Nrwl. After Jeff left, David took over and ended up rewriting the entire library. He explains some of the mistakes that they made that led to the rewrite and how he fixed them.    The panel wonders at David about using Angular Fire and NgRX. David tells the panel that the Firebase console uses NgRx under the hood and shares what he learned while working on it. Using firebase and NgRx can be very confusing because of the mass duplication of responsibility. David’s advice is to let Firebase and NgRx do their own thing and connect the dots with RxJs.    David discusses Firestore, a very advanced caching system and what you can do with it. Including, working offline and setting security rules. Frosty brings up Firebase Messaging Cues, he explains that it is similar to three-way messaging cues except its n-way. David explains that even though he is intrigued by the idea, he does not approve of the name. The panel considers possible use cases for an n-way messaging cue. David explains some of the costs and benefits of this architecture.    The episode ends with a discussion of Firebase’s documentation, which is currently a group of markdown files. David defends the simplicity of this documentation style and gives recommendations and resources for those who need more help.  Panelists Aaron Frost Brian Love Alyssa Nicoll Shai Reznik Guest David East Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://firebase.google.com/ https://firebase.google.com/summit My Angular Story https://fireship.io/ Fireship Youtube https://twitter.com/_davideast https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: Bonnie Love Aaron Frost: Stop shaming people Miss Saigon Alyssa Nicoll: David East David East: Alyssa Nicoll Freakonomics The Signal and the Noise: Why So Many Predictions Fail-But Some Don't  

In this episode of Adventures in Angular the panel has fun interviewing David East about Firebase. David starts by sharing what it was like at the recent Firebase Summit in Madrid. There were so many announcements they had a tough time fitting them all into the one-hour keynote address.    One of the cool new features announced at the Firebase Summit is Firebase Extension, David describes it as serverless without any code. The panel discusses this feature and how it works. Another cool feature announced is Google Analytics for Firebase. This allows you to use Firebase tools in conjunction with Google Analytics. The panel considers the smart things you can do in your app with this feature.    The next feature the panel discusses is Remote Config which allows you to store data and then pull out that information on demand. If you use the Google Analytics for Firebase you can target specific data for certain audiences. David explains that before this could only be done with native apps. He also explains how in doing this you no longer have to worry about the gtag loader and defines gtag for the panel.    The panel gets a little off track as David jokingly explains his beef with Aaron Frost, Frosty. Frosty host My Angular Story and a while back had twitted looking for awesome angular stories. David had responded but never heard back from Frosty. Frosty jokingly says he faxed an invite to David. The panel jokes about how awesome David’s episode will be and tells everyone to look out for his episode.    Getting back on track, David gives more examples of ways to use the Remote Config feature on with the Google Analytics for Firebase. Frosty confesses he needs to get better at looking at analytics. Sharing an example from a company he is currently working for, Frosty explains how they made nearly 2 million dollars just by changing the color of a button. The panel considers how minor changes like that can make such a big difference and how analytics helps you target your audience.    David shares the story behind writing Angular Fire. Jeff Cross worked on the angular team and started writing angular fire but then left for Nrwl. After Jeff left, David took over and ended up rewriting the entire library. He explains some of the mistakes that they made that led to the rewrite and how he fixed them.    The panel wonders at David about using Angular Fire and NgRX. David tells the panel that the Firebase console uses NgRx under the hood and shares what he learned while working on it. Using firebase and NgRx can be very confusing because of the mass duplication of responsibility. David’s advice is to let Firebase and NgRx do their own thing and connect the dots with RxJs.    David discusses Firestore, a very advanced caching system and what you can do with it. Including, working offline and setting security rules. Frosty brings up Firebase Messaging Cues, he explains that it is similar to three-way messaging cues except its n-way. David explains that even though he is intrigued by the idea, he does not approve of the name. The panel considers possible use cases for an n-way messaging cue. David explains some of the costs and benefits of this architecture.    The episode ends with a discussion of Firebase’s documentation, which is currently a group of markdown files. David defends the simplicity of this documentation style and gives recommendations and resources for those who need more help.  Panelists Aaron Frost Brian Love Alyssa Nicoll Shai Reznik Guest David East Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://firebase.google.com/ https://firebase.google.com/summit My Angular Story https://fireship.io/ Fireship Youtube https://twitter.com/_davideast https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: Bonnie Love Aaron Frost: Stop shaming people Miss Saigon Alyssa Nicoll: David East David East: Alyssa Nicoll Freakonomics The Signal and the Noise: Why So Many Predictions Fail-But Some Don't  

In this episode of Adventures in Angular the panel interviews Zama Khan Mohammed about his recent book and other open source work he has done in the Angular community. Zama explains what is so different about his book and why it is worth reading. His book takes an approach different than the common practice of walking readers through concepts, instead, his book walks readers through using a project perspective.    The first chapter walks through setting up Angular, installing Angular CLI and Angular console. After the set up is complete he walks readers through a very basic flashbase application. Zama explains how this first chapter is geared toward beginners. In his book, Zama shows users how to use the whole platform. He covers PWA and how to create brand new projects from scratch.     The panel asks him about his unique project perspective strategy for this book. Each chapter of Zama’s book walks the readers through a different project, unlike most technical books that walk readers through one project introducing a different concept each chapter. Zama explains why he wrote the book this way. He wanted to bring different libraries and tools into each project to highlight how deep and rich the Angular community and ecosystem are. The panel shares how the ecosystem and community make Angular so great to use.    Zama’s book is called Angular Projects and was published by Packt Publishing. Zama shares where to find it for those interested. The panel considers how hard writing a book must be. Zama explains the time and stress involved in writing a book. He admits he has been approached to write more books but has resolved to wait a bit before diving back into writing.    The panel discusses Zama’s open source efforts in the Angular community. They consider a few of his projects including, ngx-formly, codelyzer, and ngx-loading. He wrote ngx-formly after using formerly and he decided he wanted to use it with Angular 2.0. The panel was impressed with his contributions to codelyzer, where he helped with the accessibility requirements.    After using react-loadable Zama knew he wanted a similar feature in Angular to provide more control over loading so he built ngx-loadable. The panel defines lazy loading for listeners and explains how having control over what can load and how fast it can load can be useful in applications. Zama shares some of the improvements he has made in version 2.0.    Zama shares his hopes for speaking at ng-conf 2020, this takes the panel down a tangent discussing the exciting workshops that will be at ng-conf next year. Brian Love will be teaching a two-day workshop on Angular fundamentals. Aaron Frost is teaching and observables class and a reactive angular class. They advise everyone to buy an ng-conf ticket and not to be afraid to submit a CFP.    Back on topic, Zama shares the challenges in writing, publishing and maintaining an opensource library. He explains how contributing to open source is a great way to learn and a great way to see what a framework can do. He shares advice for those looking to get into open source and invites everyone to try Hacktoberfest.   Panelists Aaron Frost Brian Love Guest Zama Khan Mohammed Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://angularprojects.com/ https://twitter.com/mgechev https://github.com/mohammedzamakhan https://www.ng-conf.org/ https://hacktoberfest.digitalocean.com/ https://m.hero.dev/ngstory  https://github.com/aaronfrost Audit your Angular app's accessibility with codelyzer https://twitter.com/mohamedzamakhan?lang=en  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: ng-conf: CFP Office Hours Aaron Frost: Late Night with Seth Meyers Zama Khan Mohammed: Hacking the Angular Compiler

In this episode of Adventures in Angular the panel interviews Zama Khan Mohammed about his recent book and other open source work he has done in the Angular community. Zama explains what is so different about his book and why it is worth reading. His book takes an approach different than the common practice of walking readers through concepts, instead, his book walks readers through using a project perspective.    The first chapter walks through setting up Angular, installing Angular CLI and Angular console. After the set up is complete he walks readers through a very basic flashbase application. Zama explains how this first chapter is geared toward beginners. In his book, Zama shows users how to use the whole platform. He covers PWA and how to create brand new projects from scratch.     The panel asks him about his unique project perspective strategy for this book. Each chapter of Zama’s book walks the readers through a different project, unlike most technical books that walk readers through one project introducing a different concept each chapter. Zama explains why he wrote the book this way. He wanted to bring different libraries and tools into each project to highlight how deep and rich the Angular community and ecosystem are. The panel shares how the ecosystem and community make Angular so great to use.    Zama’s book is called Angular Projects and was published by Packt Publishing. Zama shares where to find it for those interested. The panel considers how hard writing a book must be. Zama explains the time and stress involved in writing a book. He admits he has been approached to write more books but has resolved to wait a bit before diving back into writing.    The panel discusses Zama’s open source efforts in the Angular community. They consider a few of his projects including, ngx-formly, codelyzer, and ngx-loading. He wrote ngx-formly after using formerly and he decided he wanted to use it with Angular 2.0. The panel was impressed with his contributions to codelyzer, where he helped with the accessibility requirements.    After using react-loadable Zama knew he wanted a similar feature in Angular to provide more control over loading so he built ngx-loadable. The panel defines lazy loading for listeners and explains how having control over what can load and how fast it can load can be useful in applications. Zama shares some of the improvements he has made in version 2.0.    Zama shares his hopes for speaking at ng-conf 2020, this takes the panel down a tangent discussing the exciting workshops that will be at ng-conf next year. Brian Love will be teaching a two-day workshop on Angular fundamentals. Aaron Frost is teaching and observables class and a reactive angular class. They advise everyone to buy an ng-conf ticket and not to be afraid to submit a CFP.    Back on topic, Zama shares the challenges in writing, publishing and maintaining an opensource library. He explains how contributing to open source is a great way to learn and a great way to see what a framework can do. He shares advice for those looking to get into open source and invites everyone to try Hacktoberfest.   Panelists Aaron Frost Brian Love Guest Zama Khan Mohammed Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://angularprojects.com/ https://twitter.com/mgechev https://github.com/mohammedzamakhan https://www.ng-conf.org/ https://hacktoberfest.digitalocean.com/ https://m.hero.dev/ngstory  https://github.com/aaronfrost Audit your Angular app's accessibility with codelyzer https://twitter.com/mohamedzamakhan?lang=en  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: ng-conf: CFP Office Hours Aaron Frost: Late Night with Seth Meyers Zama Khan Mohammed: Hacking the Angular Compiler

In this episode of Adventures in Angular the panel interviews Zama Khan Mohammed about his recent book and other open source work he has done in the Angular community. Zama explains what is so different about his book and why it is worth reading. His book takes an approach different than the common practice of walking readers through concepts, instead, his book walks readers through using a project perspective.    The first chapter walks through setting up Angular, installing Angular CLI and Angular console. After the set up is complete he walks readers through a very basic flashbase application. Zama explains how this first chapter is geared toward beginners. In his book, Zama shows users how to use the whole platform. He covers PWA and how to create brand new projects from scratch.     The panel asks him about his unique project perspective strategy for this book. Each chapter of Zama’s book walks the readers through a different project, unlike most technical books that walk readers through one project introducing a different concept each chapter. Zama explains why he wrote the book this way. He wanted to bring different libraries and tools into each project to highlight how deep and rich the Angular community and ecosystem are. The panel shares how the ecosystem and community make Angular so great to use.    Zama’s book is called Angular Projects and was published by Packt Publishing. Zama shares where to find it for those interested. The panel considers how hard writing a book must be. Zama explains the time and stress involved in writing a book. He admits he has been approached to write more books but has resolved to wait a bit before diving back into writing.    The panel discusses Zama’s open source efforts in the Angular community. They consider a few of his projects including, ngx-formly, codelyzer, and ngx-loading. He wrote ngx-formly after using formerly and he decided he wanted to use it with Angular 2.0. The panel was impressed with his contributions to codelyzer, where he helped with the accessibility requirements.    After using react-loadable Zama knew he wanted a similar feature in Angular to provide more control over loading so he built ngx-loadable. The panel defines lazy loading for listeners and explains how having control over what can load and how fast it can load can be useful in applications. Zama shares some of the improvements he has made in version 2.0.    Zama shares his hopes for speaking at ng-conf 2020, this takes the panel down a tangent discussing the exciting workshops that will be at ng-conf next year. Brian Love will be teaching a two-day workshop on Angular fundamentals. Aaron Frost is teaching and observables class and a reactive angular class. They advise everyone to buy an ng-conf ticket and not to be afraid to submit a CFP.    Back on topic, Zama shares the challenges in writing, publishing and maintaining an opensource library. He explains how contributing to open source is a great way to learn and a great way to see what a framework can do. He shares advice for those looking to get into open source and invites everyone to try Hacktoberfest.   Panelists Aaron Frost Brian Love Guest Zama Khan Mohammed Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://angularprojects.com/ https://twitter.com/mgechev https://github.com/mohammedzamakhan https://www.ng-conf.org/ https://hacktoberfest.digitalocean.com/ https://m.hero.dev/ngstory  https://github.com/aaronfrost Audit your Angular app's accessibility with codelyzer https://twitter.com/mohamedzamakhan?lang=en  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: ng-conf: CFP Office Hours Aaron Frost: Late Night with Seth Meyers Zama Khan Mohammed: Hacking the Angular Compiler

In this week’s episode of Adventures in Angular the panel has fun interviewing Narwhal rocks star and NgRx expert, Wes Grimes. Wes starts by sharing how he got started in NgRx. In a previous company, Wes was the lead architect for a project that had need of a state management solution, so it was his job to figure out how to use NgRx. While figuring it out he created a structure for using NgRx and used that structure to write a blog article about best practices for NgRx.    This blog article took the world by a storm and now has over 200,00 views. People are now building libraries and courses based on his article. The panel has a little considering the possible searches that lead people to his article. Jennifer Wadella shares some of the weirder searches that have led people to her posts. After their fun, the panel tries to get back on track.    This article thrust Wes into the world of helping people understand NgRx, what he calls a mystical machine. He explains how this article was only the beginning of learning NgRx and that he is currently working on revising that first post. The main point covered in the article was how to organize the store and how to store it in the file system. It walks through creating angular modules for each slice of the store. The second point is covers heavily is the use of barrels.   The biggest problem Wes see people run into in NgRx is they do not know where all their actions are. He shares the solution he uses for this problem, using a public API to group actions so they are easier to find. The panel expresses their frustration with the hard time the CLI has with barrel files. Wes explains why this is a common problem and shares a solution.    The panel asks for other gotcha’s to watch for when using NgRx. Wes explains how and what developers miss out on when they fail to use selectors to their fullest. When selectors are used correctly and completely developers receive all the benefits of the testing they do on NgRx. The other benefits are builtin memoization and reusability.    Another gotcha he warns against is using facades before fully understanding NgRx. This really fires up the panel, who then debates the use of facades in NgRx. Aaron Frost expresses his opinion that NgRx isn’t for everything and that by using facades you may not need to use NgRx. Wes explains that the large companies he works for are already committed to NgRx as their solution and he advises them not to use facades.   Wes explains the downsides of using NgRx, the first is when developers jump in before they understand it and back themselves into a corner. Another downside is the upfront investment cost when learning NgRx.    The panel jumps in wondering what Wes thinks of hiding those developers unfamiliar in NgRx with a facade. Wes explains how in doing this the team would be compromising architecture in order to avoid teaching developers to use NgRx properly. He clarifies that he doesn’t think facades are bad but in order to use them correctly in NgRx developers must first understand how NgRx works. Aaron explains why when working with developers unfamiliar with angular he advises them not to learn NgRx right away.   Wes shares how he has seen developers misuse facades. When using a facade it entices developers to hop back and for between imperative and declarative code. Aaron jumps in and explains that imperative code in reactive programming is very bad. He invites listeners to go out and learn more about this because it is very important to understand.    The panel considers strategies to help teams code reactively. Wes recommends requesting data from the server. This pattern is straight forward to implement and handles a lot of the common use cases in the store. Aaron suggests turning off default change detection, doing so will force the programmers to code reactively. Another way suggested is to structure teams separating concerns.    The episode ends with Wes sharing his experience joining the NgRx core team by working in the documentation, filling in gaps that he found. He also shares what will be coming to NgRx. The platform will be expanding beyond just state management, supplying reactive libraries for angular. They are also getting ready for an experimental release of NgRx component.  Panelists Aaron Frost Brian Love Jennifer Wadella Shai Reznik Alyssa Nicoll Guest Wes Grimes Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links NgRx — Best Practices for Enterprise Angular Applications  The Facade of NgRx Facades  Building with Ivy: rethinking reactive Angular | Mike Ryan | #AngularConnect 2019  https://twitter.com/wesgrimes https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: The Great Hack Shai Reznik: RxJS: A Better Way To Write Frontend Applications - Hannah Howard - JSConf US 2018  Complex Features Made Easy With RxJS - Ben Lesh  Aaron Frost: Lizzo Jennifer Wadella: https://twitter.com/began_7/status/1177880930549223424  https://github.com/vmbrasseur/Public_Speaking  Wes Grimes: ngGirls

In this week’s episode of Adventures in Angular the panel has fun interviewing Narwhal rocks star and NgRx expert, Wes Grimes. Wes starts by sharing how he got started in NgRx. In a previous company, Wes was the lead architect for a project that had need of a state management solution, so it was his job to figure out how to use NgRx. While figuring it out he created a structure for using NgRx and used that structure to write a blog article about best practices for NgRx.    This blog article took the world by a storm and now has over 200,00 views. People are now building libraries and courses based on his article. The panel has a little considering the possible searches that lead people to his article. Jennifer Wadella shares some of the weirder searches that have led people to her posts. After their fun, the panel tries to get back on track.    This article thrust Wes into the world of helping people understand NgRx, what he calls a mystical machine. He explains how this article was only the beginning of learning NgRx and that he is currently working on revising that first post. The main point covered in the article was how to organize the store and how to store it in the file system. It walks through creating angular modules for each slice of the store. The second point is covers heavily is the use of barrels.   The biggest problem Wes see people run into in NgRx is they do not know where all their actions are. He shares the solution he uses for this problem, using a public API to group actions so they are easier to find. The panel expresses their frustration with the hard time the CLI has with barrel files. Wes explains why this is a common problem and shares a solution.    The panel asks for other gotcha’s to watch for when using NgRx. Wes explains how and what developers miss out on when they fail to use selectors to their fullest. When selectors are used correctly and completely developers receive all the benefits of the testing they do on NgRx. The other benefits are builtin memoization and reusability.    Another gotcha he warns against is using facades before fully understanding NgRx. This really fires up the panel, who then debates the use of facades in NgRx. Aaron Frost expresses his opinion that NgRx isn’t for everything and that by using facades you may not need to use NgRx. Wes explains that the large companies he works for are already committed to NgRx as their solution and he advises them not to use facades.   Wes explains the downsides of using NgRx, the first is when developers jump in before they understand it and back themselves into a corner. Another downside is the upfront investment cost when learning NgRx.    The panel jumps in wondering what Wes thinks of hiding those developers unfamiliar in NgRx with a facade. Wes explains how in doing this the team would be compromising architecture in order to avoid teaching developers to use NgRx properly. He clarifies that he doesn’t think facades are bad but in order to use them correctly in NgRx developers must first understand how NgRx works. Aaron explains why when working with developers unfamiliar with angular he advises them not to learn NgRx right away.   Wes shares how he has seen developers misuse facades. When using a facade it entices developers to hop back and for between imperative and declarative code. Aaron jumps in and explains that imperative code in reactive programming is very bad. He invites listeners to go out and learn more about this because it is very important to understand.    The panel considers strategies to help teams code reactively. Wes recommends requesting data from the server. This pattern is straight forward to implement and handles a lot of the common use cases in the store. Aaron suggests turning off default change detection, doing so will force the programmers to code reactively. Another way suggested is to structure teams separating concerns.    The episode ends with Wes sharing his experience joining the NgRx core team by working in the documentation, filling in gaps that he found. He also shares what will be coming to NgRx. The platform will be expanding beyond just state management, supplying reactive libraries for angular. They are also getting ready for an experimental release of NgRx component.  Panelists Aaron Frost Brian Love Jennifer Wadella Shai Reznik Alyssa Nicoll Guest Wes Grimes Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links NgRx — Best Practices for Enterprise Angular Applications  The Facade of NgRx Facades  Building with Ivy: rethinking reactive Angular | Mike Ryan | #AngularConnect 2019  https://twitter.com/wesgrimes https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: The Great Hack Shai Reznik: RxJS: A Better Way To Write Frontend Applications - Hannah Howard - JSConf US 2018  Complex Features Made Easy With RxJS - Ben Lesh  Aaron Frost: Lizzo Jennifer Wadella: https://twitter.com/began_7/status/1177880930549223424  https://github.com/vmbrasseur/Public_Speaking  Wes Grimes: ngGirls

In this week’s episode of Adventures in Angular the panel has fun interviewing Narwhal rocks star and NgRx expert, Wes Grimes. Wes starts by sharing how he got started in NgRx. In a previous company, Wes was the lead architect for a project that had need of a state management solution, so it was his job to figure out how to use NgRx. While figuring it out he created a structure for using NgRx and used that structure to write a blog article about best practices for NgRx.    This blog article took the world by a storm and now has over 200,00 views. People are now building libraries and courses based on his article. The panel has a little considering the possible searches that lead people to his article. Jennifer Wadella shares some of the weirder searches that have led people to her posts. After their fun, the panel tries to get back on track.    This article thrust Wes into the world of helping people understand NgRx, what he calls a mystical machine. He explains how this article was only the beginning of learning NgRx and that he is currently working on revising that first post. The main point covered in the article was how to organize the store and how to store it in the file system. It walks through creating angular modules for each slice of the store. The second point is covers heavily is the use of barrels.   The biggest problem Wes see people run into in NgRx is they do not know where all their actions are. He shares the solution he uses for this problem, using a public API to group actions so they are easier to find. The panel expresses their frustration with the hard time the CLI has with barrel files. Wes explains why this is a common problem and shares a solution.    The panel asks for other gotcha’s to watch for when using NgRx. Wes explains how and what developers miss out on when they fail to use selectors to their fullest. When selectors are used correctly and completely developers receive all the benefits of the testing they do on NgRx. The other benefits are builtin memoization and reusability.    Another gotcha he warns against is using facades before fully understanding NgRx. This really fires up the panel, who then debates the use of facades in NgRx. Aaron Frost expresses his opinion that NgRx isn’t for everything and that by using facades you may not need to use NgRx. Wes explains that the large companies he works for are already committed to NgRx as their solution and he advises them not to use facades.   Wes explains the downsides of using NgRx, the first is when developers jump in before they understand it and back themselves into a corner. Another downside is the upfront investment cost when learning NgRx.    The panel jumps in wondering what Wes thinks of hiding those developers unfamiliar in NgRx with a facade. Wes explains how in doing this the team would be compromising architecture in order to avoid teaching developers to use NgRx properly. He clarifies that he doesn’t think facades are bad but in order to use them correctly in NgRx developers must first understand how NgRx works. Aaron explains why when working with developers unfamiliar with angular he advises them not to learn NgRx right away.   Wes shares how he has seen developers misuse facades. When using a facade it entices developers to hop back and for between imperative and declarative code. Aaron jumps in and explains that imperative code in reactive programming is very bad. He invites listeners to go out and learn more about this because it is very important to understand.    The panel considers strategies to help teams code reactively. Wes recommends requesting data from the server. This pattern is straight forward to implement and handles a lot of the common use cases in the store. Aaron suggests turning off default change detection, doing so will force the programmers to code reactively. Another way suggested is to structure teams separating concerns.    The episode ends with Wes sharing his experience joining the NgRx core team by working in the documentation, filling in gaps that he found. He also shares what will be coming to NgRx. The platform will be expanding beyond just state management, supplying reactive libraries for angular. They are also getting ready for an experimental release of NgRx component.  Panelists Aaron Frost Brian Love Jennifer Wadella Shai Reznik Alyssa Nicoll Guest Wes Grimes Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links NgRx — Best Practices for Enterprise Angular Applications  The Facade of NgRx Facades  Building with Ivy: rethinking reactive Angular | Mike Ryan | #AngularConnect 2019  https://twitter.com/wesgrimes https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: The Great Hack Shai Reznik: RxJS: A Better Way To Write Frontend Applications - Hannah Howard - JSConf US 2018  Complex Features Made Easy With RxJS - Ben Lesh  Aaron Frost: Lizzo Jennifer Wadella: https://twitter.com/began_7/status/1177880930549223424  https://github.com/vmbrasseur/Public_Speaking  Wes Grimes: ngGirls

In this week’s episode of Adventures in Angular the panel interviews Shlomi Assaf, talking about ngrid. After some playful banter about the naming of Ngrid, Shlomi shares the reasons behind building ngrid. The company he was working for at the time need a grid, he tested nggrid but wanted something completely opensource, so he built one. He also explains that nggrid caused some problems in their project which made him want something more customizable.   Shlomi explains how much work is needed on the application and asks listeners to contribute to documentation or other areas of the project. Shai Reznik endorses Shlomi as one of the smartest peoples he knows and tells listeners if they want to learn from someone who knows a lot about angular to step up and join this project.    The panel asks about the challenges Shlomi faced while building this app and what it was like using the CDK. Nggrid has a how company working on it but ngrid has only Shlomi. Shlomi explains that the CDK had a lot of the building blocks need to building blocks to build this application and was the power behind the project. The CDK’s lacks the ability to extend easily which was a challenge. He explains that his biggest frustration while building the application was the drag and drop feature.    Shlomi shares many of the features he built into the application that even though he built it over a three year period he could do it piece by piece because of the way he designed it. He considers the selling points of the application and shares them with the panel. Shlomi compares ngrid to other grid, explaining how templating, creating columns and pagination are all made easier with ngrid. With ngrid there is also virtual scrolling and you can control the width of each column.    Next, the pane considers performance, asking how the grid would handle if you loaded thousand or even tens of thousands of records and data onto the grid. Shlomi explains that unless the cells were extremely complex that ngrid’s performance would not suffer. The panel how ngrid could work with serverside rendering but not with NativeScript. Shlomi explains version support and advises listeners to use Angular 8.   The panel ends the episode by sharing information about next year's ng-conf. Tickets go on sale on October 1, 2019, the best deals go fast so watch out for them. Many of the panel will be there, Brian Love will be giving the Angular Fundamentals Two-Day Workshop. The CFP also opens October 1, 2019, and will close January 1, 2019. Aaron Frost invites anyone who would like to submit to reach out to the veteran panelists to nail down ideas for their conference proposals. He also recommends submitting more than one.    Panelists Aaron Frost Brian Love Jennifer Wadella Shai Reznik Alyssa Nicoll Guest Shlomi Assaf Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links https://www.npmjs.com/package/@pebula/ngrid  https://shlomiassaf.github.io/ngrid/  https://www.ng-conf.org/speakers/  https://twitter.com/aaronfrost https://twitter.com/brian_love?lang=en https://twitter.com/AlyssaNicoll?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor https://twitter.com/shai_reznik?lang=en https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: NG-DE 2019  Angular Connect Shai Reznik: The magic of RXJS sharing operators and their differences Let Me Off at the Top!: My Classy Life and Other Musings  Aaron Frost: Connecting with your children Shlomi Assaf: How we make Angular fast | Miško Hevery

In this week’s episode of Adventures in Angular the panel interviews Shlomi Assaf, talking about ngrid. After some playful banter about the naming of Ngrid, Shlomi shares the reasons behind building ngrid. The company he was working for at the time need a grid, he tested nggrid but wanted something completely opensource, so he built one. He also explains that nggrid caused some problems in their project which made him want something more customizable.   Shlomi explains how much work is needed on the application and asks listeners to contribute to documentation or other areas of the project. Shai Reznik endorses Shlomi as one of the smartest peoples he knows and tells listeners if they want to learn from someone who knows a lot about angular to step up and join this project.    The panel asks about the challenges Shlomi faced while building this app and what it was like using the CDK. Nggrid has a how company working on it but ngrid has only Shlomi. Shlomi explains that the CDK had a lot of the building blocks need to building blocks to build this application and was the power behind the project. The CDK’s lacks the ability to extend easily which was a challenge. He explains that his biggest frustration while building the application was the drag and drop feature.    Shlomi shares many of the features he built into the application that even though he built it over a three year period he could do it piece by piece because of the way he designed it. He considers the selling points of the application and shares them with the panel. Shlomi compares ngrid to other grid, explaining how templating, creating columns and pagination are all made easier with ngrid. With ngrid there is also virtual scrolling and you can control the width of each column.    Next, the pane considers performance, asking how the grid would handle if you loaded thousand or even tens of thousands of records and data onto the grid. Shlomi explains that unless the cells were extremely complex that ngrid’s performance would not suffer. The panel how ngrid could work with serverside rendering but not with NativeScript. Shlomi explains version support and advises listeners to use Angular 8.   The panel ends the episode by sharing information about next year's ng-conf. Tickets go on sale on October 1, 2019, the best deals go fast so watch out for them. Many of the panel will be there, Brian Love will be giving the Angular Fundamentals Two-Day Workshop. The CFP also opens October 1, 2019, and will close January 1, 2019. Aaron Frost invites anyone who would like to submit to reach out to the veteran panelists to nail down ideas for their conference proposals. He also recommends submitting more than one.    Panelists Aaron Frost Brian Love Jennifer Wadella Shai Reznik Alyssa Nicoll Guest Shlomi Assaf Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links https://www.npmjs.com/package/@pebula/ngrid  https://shlomiassaf.github.io/ngrid/  https://www.ng-conf.org/speakers/  https://twitter.com/aaronfrost https://twitter.com/brian_love?lang=en https://twitter.com/AlyssaNicoll?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor https://twitter.com/shai_reznik?lang=en https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: NG-DE 2019  Angular Connect Shai Reznik: The magic of RXJS sharing operators and their differences Let Me Off at the Top!: My Classy Life and Other Musings  Aaron Frost: Connecting with your children Shlomi Assaf: How we make Angular fast | Miško Hevery

In this week’s episode of Adventures in Angular the panel interviews Shlomi Assaf, talking about ngrid. After some playful banter about the naming of Ngrid, Shlomi shares the reasons behind building ngrid. The company he was working for at the time need a grid, he tested nggrid but wanted something completely opensource, so he built one. He also explains that nggrid caused some problems in their project which made him want something more customizable.   Shlomi explains how much work is needed on the application and asks listeners to contribute to documentation or other areas of the project. Shai Reznik endorses Shlomi as one of the smartest peoples he knows and tells listeners if they want to learn from someone who knows a lot about angular to step up and join this project.    The panel asks about the challenges Shlomi faced while building this app and what it was like using the CDK. Nggrid has a how company working on it but ngrid has only Shlomi. Shlomi explains that the CDK had a lot of the building blocks need to building blocks to build this application and was the power behind the project. The CDK’s lacks the ability to extend easily which was a challenge. He explains that his biggest frustration while building the application was the drag and drop feature.    Shlomi shares many of the features he built into the application that even though he built it over a three year period he could do it piece by piece because of the way he designed it. He considers the selling points of the application and shares them with the panel. Shlomi compares ngrid to other grid, explaining how templating, creating columns and pagination are all made easier with ngrid. With ngrid there is also virtual scrolling and you can control the width of each column.    Next, the pane considers performance, asking how the grid would handle if you loaded thousand or even tens of thousands of records and data onto the grid. Shlomi explains that unless the cells were extremely complex that ngrid’s performance would not suffer. The panel how ngrid could work with serverside rendering but not with NativeScript. Shlomi explains version support and advises listeners to use Angular 8.   The panel ends the episode by sharing information about next year's ng-conf. Tickets go on sale on October 1, 2019, the best deals go fast so watch out for them. Many of the panel will be there, Brian Love will be giving the Angular Fundamentals Two-Day Workshop. The CFP also opens October 1, 2019, and will close January 1, 2019. Aaron Frost invites anyone who would like to submit to reach out to the veteran panelists to nail down ideas for their conference proposals. He also recommends submitting more than one.    Panelists Aaron Frost Brian Love Jennifer Wadella Shai Reznik Alyssa Nicoll Guest Shlomi Assaf Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links https://www.npmjs.com/package/@pebula/ngrid  https://shlomiassaf.github.io/ngrid/  https://www.ng-conf.org/speakers/  https://twitter.com/aaronfrost https://twitter.com/brian_love?lang=en https://twitter.com/AlyssaNicoll?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor https://twitter.com/shai_reznik?lang=en https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: NG-DE 2019  Angular Connect Shai Reznik: The magic of RXJS sharing operators and their differences Let Me Off at the Top!: My Classy Life and Other Musings  Aaron Frost: Connecting with your children Shlomi Assaf: How we make Angular fast | Miško Hevery

In this week’s episode of Adventures in Angular the panel interviews Manfred Steyer, the creator of ngx-build-plus and angular architecture expert and consultant. Ngx-build-plus is a way to extend how the CLI is doing its build. Manfred explains how ngx-build plus works in two different ways. The first is that it provides a partial webpack configurations file that merges with the webpack configuration that the CLI is using. The second, it provides a plugin with free methods that influence the CLI.    Manfred consults with companies on architecture, he explains that the main problem when people take a simple application and make it complex, big, with a lot of entities and forms. This makes it difficult to manage in the long term. He borrows ideas from domain-driven design to help these companies structure their applications.    Strategic domain-driven design is one of the main strategies he uses when structuring an application. Strategic domain-driven design is subdividing a big application into subdomains, then modeling those subdomains separately. By modeling the separately, the coupling is limited. This makes it easier to change parts of the code without breaking anything unrelated in the application.    The panel asks Manfred for recommendations for using domain-driven design in their architecture. Manfred recommends using libraries within monorepos and outlines the benefits. Using this method creates isolation, you can’t easily access everything in the library because of the public API. Manfred explains how a public API works like a facade.    Nx is the recommended tool for the monorepos, as it adds many great features to the CLI and is not as heavyweight as other monorepo solutions. Manfred explains one of his favorite features called tagging. This restricts which libraries can access another library. The panel discusses some examples of tagging.    The panel wonders about Manfred’s opinions on state management solutions. Manfred explains that he doesn’t believe that every application needs a state management solution. When used at the wrong time a state management solution is an overkill. He also explains that not using a state management library does not make someone a bad person.   The panel discusses how you know if you need a state management solution. Manfred indicates two things to look for when considering the use of a state management library. First, is there a lot of state? Second, is the state going to be used by many different components?    If you are not sure he recommends starting with a facade and adding a state management library later if needed.  The panel explains what a facade is. A facade is when you combine a lot of systems under a single API, like jquery. Manfred gives an example of what a management facade should look like. The panel shares experiences explaining how it works and gives advice and examples of using a facade.    The topic turns to the importance of testing. Manfred shares his testing philosophy, asking how do you sleep at night knowing you have to change a part of the application? Does it scare you because you know you are going to break everything in a terrible and painful way? Or, Do sleep soundly because you know you are safe to do what needs to be done. Shai Reznik equates this to the shake meter, how much does your hand shake when you push the button to execute a change.   Manfred’s recommends starting with unit testing, testing where you need it and avoid a testing coverage goal. Unit testing he explains are more stable than end-to-end testing. You do need end-to-end testing but very little in comparison to unit testing. Aaron Frost shares the tool protractor flake as a way to combat the flakiness of end-to-end testing.   Manfred explains that there are two common mistakes people make in their angular architecture. The first is over-engineering and under-engineering an application. He explains the problems that arise with each and how to combat this problem. The sweet spot can be found by knowing what you want, finding the right structuring to fit what you want.    The panel wonders how to measure the cleanliness of code in an application. Manfred recommends looking at each indirection and deciding if it is necessary. The panel explains what indirections are, an example is event mechanisms, you can’t see a direct effect. The panel discusses NgRx as an indirection framework. Manfred warns not to use NgRx all the time only when you need it.   This launches the panel onto a tangent of choosing tools and how to weight the pros and cons of each tool. The phrase “use it when you need it” is considered by the panel, the genericness of the phrase is discusses. The panel advises new developers who don’t have the experience to gauge if they need something or not to do the research necessary to understand a tool and to experiment with it.    The panel comes back to the other common mistake made with architecture which is chatty applications. Applications that send thousands of requests to the backend causing the application to slow. The panel considers why this happens. Aaron explains the concept of affordance and how this results in chatty applications.  Panelists Aaron Frost Brian Love Shai Reznik Guest Manfred Steyer Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links NgRx + Facades: Better State Management https://www.npmjs.com/package/protractor-flake https://twitter.com/manfredsteyer?lang=en https://www.softwarearchitekt.at/ https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: The 5 Big Features of TypeScript 3.7 and How to Use Them  Shai Reznik: Angular Testing Course Hip-Hop Evolution Aaron Frost: RxJs Live  Lover  Manfred Steyer: Star Trek: Picard ngrx-etc  

In this week’s episode of Adventures in Angular the panel interviews Manfred Steyer, the creator of ngx-build-plus and angular architecture expert and consultant. Ngx-build-plus is a way to extend how the CLI is doing its build. Manfred explains how ngx-build plus works in two different ways. The first is that it provides a partial webpack configurations file that merges with the webpack configuration that the CLI is using. The second, it provides a plugin with free methods that influence the CLI.    Manfred consults with companies on architecture, he explains that the main problem when people take a simple application and make it complex, big, with a lot of entities and forms. This makes it difficult to manage in the long term. He borrows ideas from domain-driven design to help these companies structure their applications.    Strategic domain-driven design is one of the main strategies he uses when structuring an application. Strategic domain-driven design is subdividing a big application into subdomains, then modeling those subdomains separately. By modeling the separately, the coupling is limited. This makes it easier to change parts of the code without breaking anything unrelated in the application.    The panel asks Manfred for recommendations for using domain-driven design in their architecture. Manfred recommends using libraries within monorepos and outlines the benefits. Using this method creates isolation, you can’t easily access everything in the library because of the public API. Manfred explains how a public API works like a facade.    Nx is the recommended tool for the monorepos, as it adds many great features to the CLI and is not as heavyweight as other monorepo solutions. Manfred explains one of his favorite features called tagging. This restricts which libraries can access another library. The panel discusses some examples of tagging.    The panel wonders about Manfred’s opinions on state management solutions. Manfred explains that he doesn’t believe that every application needs a state management solution. When used at the wrong time a state management solution is an overkill. He also explains that not using a state management library does not make someone a bad person.   The panel discusses how you know if you need a state management solution. Manfred indicates two things to look for when considering the use of a state management library. First, is there a lot of state? Second, is the state going to be used by many different components?    If you are not sure he recommends starting with a facade and adding a state management library later if needed.  The panel explains what a facade is. A facade is when you combine a lot of systems under a single API, like jquery. Manfred gives an example of what a management facade should look like. The panel shares experiences explaining how it works and gives advice and examples of using a facade.    The topic turns to the importance of testing. Manfred shares his testing philosophy, asking how do you sleep at night knowing you have to change a part of the application? Does it scare you because you know you are going to break everything in a terrible and painful way? Or, Do sleep soundly because you know you are safe to do what needs to be done. Shai Reznik equates this to the shake meter, how much does your hand shake when you push the button to execute a change.   Manfred’s recommends starting with unit testing, testing where you need it and avoid a testing coverage goal. Unit testing he explains are more stable than end-to-end testing. You do need end-to-end testing but very little in comparison to unit testing. Aaron Frost shares the tool protractor flake as a way to combat the flakiness of end-to-end testing.   Manfred explains that there are two common mistakes people make in their angular architecture. The first is over-engineering and under-engineering an application. He explains the problems that arise with each and how to combat this problem. The sweet spot can be found by knowing what you want, finding the right structuring to fit what you want.    The panel wonders how to measure the cleanliness of code in an application. Manfred recommends looking at each indirection and deciding if it is necessary. The panel explains what indirections are, an example is event mechanisms, you can’t see a direct effect. The panel discusses NgRx as an indirection framework. Manfred warns not to use NgRx all the time only when you need it.   This launches the panel onto a tangent of choosing tools and how to weight the pros and cons of each tool. The phrase “use it when you need it” is considered by the panel, the genericness of the phrase is discusses. The panel advises new developers who don’t have the experience to gauge if they need something or not to do the research necessary to understand a tool and to experiment with it.    The panel comes back to the other common mistake made with architecture which is chatty applications. Applications that send thousands of requests to the backend causing the application to slow. The panel considers why this happens. Aaron explains the concept of affordance and how this results in chatty applications.  Panelists Aaron Frost Brian Love Shai Reznik Guest Manfred Steyer Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links NgRx + Facades: Better State Management https://www.npmjs.com/package/protractor-flake https://twitter.com/manfredsteyer?lang=en https://www.softwarearchitekt.at/ https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: The 5 Big Features of TypeScript 3.7 and How to Use Them  Shai Reznik: Angular Testing Course Hip-Hop Evolution Aaron Frost: RxJs Live  Lover  Manfred Steyer: Star Trek: Picard ngrx-etc  

In this week’s episode of Adventures in Angular the panel interviews Manfred Steyer, the creator of ngx-build-plus and angular architecture expert and consultant. Ngx-build-plus is a way to extend how the CLI is doing its build. Manfred explains how ngx-build plus works in two different ways. The first is that it provides a partial webpack configurations file that merges with the webpack configuration that the CLI is using. The second, it provides a plugin with free methods that influence the CLI.    Manfred consults with companies on architecture, he explains that the main problem when people take a simple application and make it complex, big, with a lot of entities and forms. This makes it difficult to manage in the long term. He borrows ideas from domain-driven design to help these companies structure their applications.    Strategic domain-driven design is one of the main strategies he uses when structuring an application. Strategic domain-driven design is subdividing a big application into subdomains, then modeling those subdomains separately. By modeling the separately, the coupling is limited. This makes it easier to change parts of the code without breaking anything unrelated in the application.    The panel asks Manfred for recommendations for using domain-driven design in their architecture. Manfred recommends using libraries within monorepos and outlines the benefits. Using this method creates isolation, you can’t easily access everything in the library because of the public API. Manfred explains how a public API works like a facade.    Nx is the recommended tool for the monorepos, as it adds many great features to the CLI and is not as heavyweight as other monorepo solutions. Manfred explains one of his favorite features called tagging. This restricts which libraries can access another library. The panel discusses some examples of tagging.    The panel wonders about Manfred’s opinions on state management solutions. Manfred explains that he doesn’t believe that every application needs a state management solution. When used at the wrong time a state management solution is an overkill. He also explains that not using a state management library does not make someone a bad person.   The panel discusses how you know if you need a state management solution. Manfred indicates two things to look for when considering the use of a state management library. First, is there a lot of state? Second, is the state going to be used by many different components?    If you are not sure he recommends starting with a facade and adding a state management library later if needed.  The panel explains what a facade is. A facade is when you combine a lot of systems under a single API, like jquery. Manfred gives an example of what a management facade should look like. The panel shares experiences explaining how it works and gives advice and examples of using a facade.    The topic turns to the importance of testing. Manfred shares his testing philosophy, asking how do you sleep at night knowing you have to change a part of the application? Does it scare you because you know you are going to break everything in a terrible and painful way? Or, Do sleep soundly because you know you are safe to do what needs to be done. Shai Reznik equates this to the shake meter, how much does your hand shake when you push the button to execute a change.   Manfred’s recommends starting with unit testing, testing where you need it and avoid a testing coverage goal. Unit testing he explains are more stable than end-to-end testing. You do need end-to-end testing but very little in comparison to unit testing. Aaron Frost shares the tool protractor flake as a way to combat the flakiness of end-to-end testing.   Manfred explains that there are two common mistakes people make in their angular architecture. The first is over-engineering and under-engineering an application. He explains the problems that arise with each and how to combat this problem. The sweet spot can be found by knowing what you want, finding the right structuring to fit what you want.    The panel wonders how to measure the cleanliness of code in an application. Manfred recommends looking at each indirection and deciding if it is necessary. The panel explains what indirections are, an example is event mechanisms, you can’t see a direct effect. The panel discusses NgRx as an indirection framework. Manfred warns not to use NgRx all the time only when you need it.   This launches the panel onto a tangent of choosing tools and how to weight the pros and cons of each tool. The phrase “use it when you need it” is considered by the panel, the genericness of the phrase is discusses. The panel advises new developers who don’t have the experience to gauge if they need something or not to do the research necessary to understand a tool and to experiment with it.    The panel comes back to the other common mistake made with architecture which is chatty applications. Applications that send thousands of requests to the backend causing the application to slow. The panel considers why this happens. Aaron explains the concept of affordance and how this results in chatty applications.  Panelists Aaron Frost Brian Love Shai Reznik Guest Manfred Steyer Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links NgRx + Facades: Better State Management https://www.npmjs.com/package/protractor-flake https://twitter.com/manfredsteyer?lang=en https://www.softwarearchitekt.at/ https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: The 5 Big Features of TypeScript 3.7 and How to Use Them  Shai Reznik: Angular Testing Course Hip-Hop Evolution Aaron Frost: RxJs Live  Lover  Manfred Steyer: Star Trek: Picard ngrx-etc  

Episode Summary In this episode of Adventures in Angular Tomas Trajan, an angular elements expert, breaks down how to use angular elements for the panel. Tomas explains that angular elements are great for very specific use cases.    Tomas starts by describing a scenario with a large enterprise with tens of developer teams and hundreds of developers, they have a few choices on how to organize their applications. The first option is a messy monolith. The second option is using monorepos and Nx. The final option is to use a multi-spa solution.   Tomas explains how the multi-spa solution works. This solution consists of 80 stand-alone applications, on the same page and share components. Tomas outlines the common problems when using the solutions and how using angular elements combat those problems.   The panel moves on to considers how you know if you should use angular elements in this way. Tomas provides two questions to ask yourself when deciding whether or not to use angular elements. The first question is, are you in a multi-spa scenario? The second question is, are components shared across applications? If the answer is yes for both of those questions then angular elements can only help the situation.    In last week’s episode of Adventures in Angular the panel interviewed Victor Savkin about using monorepos and Nx. The panel asks Tomas to compare the strategy of using monorepos and Nx to his strategy of using multi-spa with angular elements. He explains why an enterprise might choose multi-spa over monorepos. He also gives the reasons the organization he is working with chose to work with multi-spa.    Aaron asks for clarification for using elements in these multi-spa projects. Tomas goes into great detail, breaking down the way multi-spa and angular elements work together. They walk through it together using consumer profiles as an example.   Tomas explains that using his approach all the applications update components all at once using angular elements. The panel considers the benefits of using Tomas’s approach and which scenarios it would work best for. Aaron expresses his appreciation for all the work Tomas did and the problems he overcame then bundling his solution in a library together so developers can just use it without all the pain.      The library can be found on Github. Tomas tells the panel that there has already been some community contribution to the library. He describes some of the pull requests they have received along with the plans they have for angular elements.    The topic turns to mismatched versioning and how the bundle will work. Tomas explains that the only problem they have seen with mismatched versioning is with zone.js. He shares some workarounds to the problem and promises that they are working on a solution.    The episode ends with the panel listing all the major benefits that an enterprise can gain from using the multi-spa and angular elements approach. It will save them money, allow teams to work together, create and isolation. Tomas also shares some of the new features available in angular elements today.    Panelists Aaron Frost Brian Love Guest Tomas Trajan Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors   Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links AiA 256: Debunking Monorepo Myths with Victor Savkin https://angular-extensions.github.io/elements/  https://twitter.com/tomastrajan  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: https://node-atl.org/  Shai Reznik: https://netbasal.com/  Aaron Frost: How to Be Less Stupid About Race: On Racism, White Supremacy, and the Racial Divide Tomas Trajan: Slipknot EX

Episode Summary In this episode of Adventures in Angular Tomas Trajan, an angular elements expert, breaks down how to use angular elements for the panel. Tomas explains that angular elements are great for very specific use cases.    Tomas starts by describing a scenario with a large enterprise with tens of developer teams and hundreds of developers, they have a few choices on how to organize their applications. The first option is a messy monolith. The second option is using monorepos and Nx. The final option is to use a multi-spa solution.   Tomas explains how the multi-spa solution works. This solution consists of 80 stand-alone applications, on the same page and share components. Tomas outlines the common problems when using the solutions and how using angular elements combat those problems.   The panel moves on to considers how you know if you should use angular elements in this way. Tomas provides two questions to ask yourself when deciding whether or not to use angular elements. The first question is, are you in a multi-spa scenario? The second question is, are components shared across applications? If the answer is yes for both of those questions then angular elements can only help the situation.    In last week’s episode of Adventures in Angular the panel interviewed Victor Savkin about using monorepos and Nx. The panel asks Tomas to compare the strategy of using monorepos and Nx to his strategy of using multi-spa with angular elements. He explains why an enterprise might choose multi-spa over monorepos. He also gives the reasons the organization he is working with chose to work with multi-spa.    Aaron asks for clarification for using elements in these multi-spa projects. Tomas goes into great detail, breaking down the way multi-spa and angular elements work together. They walk through it together using consumer profiles as an example.   Tomas explains that using his approach all the applications update components all at once using angular elements. The panel considers the benefits of using Tomas’s approach and which scenarios it would work best for. Aaron expresses his appreciation for all the work Tomas did and the problems he overcame then bundling his solution in a library together so developers can just use it without all the pain.      The library can be found on Github. Tomas tells the panel that there has already been some community contribution to the library. He describes some of the pull requests they have received along with the plans they have for angular elements.    The topic turns to mismatched versioning and how the bundle will work. Tomas explains that the only problem they have seen with mismatched versioning is with zone.js. He shares some workarounds to the problem and promises that they are working on a solution.    The episode ends with the panel listing all the major benefits that an enterprise can gain from using the multi-spa and angular elements approach. It will save them money, allow teams to work together, create and isolation. Tomas also shares some of the new features available in angular elements today.    Panelists Aaron Frost Brian Love Guest Tomas Trajan Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors   Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links AiA 256: Debunking Monorepo Myths with Victor Savkin https://angular-extensions.github.io/elements/  https://twitter.com/tomastrajan  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: https://node-atl.org/  Shai Reznik: https://netbasal.com/  Aaron Frost: How to Be Less Stupid About Race: On Racism, White Supremacy, and the Racial Divide Tomas Trajan: Slipknot EX

Episode Summary In this episode of Adventures in Angular Tomas Trajan, an angular elements expert, breaks down how to use angular elements for the panel. Tomas explains that angular elements are great for very specific use cases.    Tomas starts by describing a scenario with a large enterprise with tens of developer teams and hundreds of developers, they have a few choices on how to organize their applications. The first option is a messy monolith. The second option is using monorepos and Nx. The final option is to use a multi-spa solution.   Tomas explains how the multi-spa solution works. This solution consists of 80 stand-alone applications, on the same page and share components. Tomas outlines the common problems when using the solutions and how using angular elements combat those problems.   The panel moves on to considers how you know if you should use angular elements in this way. Tomas provides two questions to ask yourself when deciding whether or not to use angular elements. The first question is, are you in a multi-spa scenario? The second question is, are components shared across applications? If the answer is yes for both of those questions then angular elements can only help the situation.    In last week’s episode of Adventures in Angular the panel interviewed Victor Savkin about using monorepos and Nx. The panel asks Tomas to compare the strategy of using monorepos and Nx to his strategy of using multi-spa with angular elements. He explains why an enterprise might choose multi-spa over monorepos. He also gives the reasons the organization he is working with chose to work with multi-spa.    Aaron asks for clarification for using elements in these multi-spa projects. Tomas goes into great detail, breaking down the way multi-spa and angular elements work together. They walk through it together using consumer profiles as an example.   Tomas explains that using his approach all the applications update components all at once using angular elements. The panel considers the benefits of using Tomas’s approach and which scenarios it would work best for. Aaron expresses his appreciation for all the work Tomas did and the problems he overcame then bundling his solution in a library together so developers can just use it without all the pain.      The library can be found on Github. Tomas tells the panel that there has already been some community contribution to the library. He describes some of the pull requests they have received along with the plans they have for angular elements.    The topic turns to mismatched versioning and how the bundle will work. Tomas explains that the only problem they have seen with mismatched versioning is with zone.js. He shares some workarounds to the problem and promises that they are working on a solution.    The episode ends with the panel listing all the major benefits that an enterprise can gain from using the multi-spa and angular elements approach. It will save them money, allow teams to work together, create and isolation. Tomas also shares some of the new features available in angular elements today.    Panelists Aaron Frost Brian Love Guest Tomas Trajan Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors   Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Cachefly Links AiA 256: Debunking Monorepo Myths with Victor Savkin https://angular-extensions.github.io/elements/  https://twitter.com/tomastrajan  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: https://node-atl.org/  Shai Reznik: https://netbasal.com/  Aaron Frost: How to Be Less Stupid About Race: On Racism, White Supremacy, and the Racial Divide Tomas Trajan: Slipknot EX

Episode Summary   Victor Savkin, former angular team member and now cofounder of Narwhal Technologies Inc or Nrwl, returns to Adventures in Angular to teach the panel about monorepos. Victor starts by explaining what monorepos are and why you might need one. Monorepo style development is when multiple projects developed in the same repository and the tools used to manage code between those apps.    There are many benefits to using monorepos as Victor explains to the panel, such as sharing code between apps. Monorepos help you see what's going on in reality as well as helps you take control of the structure of your code. It also allows for more interesting deployment strategies. Victor talks briefly about his time at Google, working on the toolchain and using a large monorepo.   After the panel asks about the costs of using a monorepo strategy, Victor explains that there are many perceived costs that are actually false or easily overcome. The first perceived cost he tells the panel about is how people get confused and believe that apps have to be deployed together when they really have to be developed in the same repository. The second is the fear of misplaced ownership, that some other developer will come along and ruin their code. Victor explains that ownership can be configured and controlled so that no one you don’t trust can touch your code.    The next myth developers believe about monorepos is that it doesn’t scale and especially when it comes to performance. Victor explains that when the app is set up correctly and testing used correctly this isn’t a problem. The final perceived cost is that Git will break. Victor debunks this by explaining that you would have to be doing extremely well in order for Git to be a bottleneck and even then there are ways around that problem.    Victor explains the one real cost and that is you have to change the way you code. The panel discusses a few different coding styles. Victor recommends getting used to single version policy and trunk-based development. He defines trunk-based development, explaining how it works and why it is better for monorepos than long-range branch development.    Victor sees two types of groups who want to get started in monorepos and he explains what they most commonly do wrong. The first is greenfield projects who jump right in without thinking about it and eventually crash. The second is teams with a giant app and through a monorepo in hoping it will help them structure their app. He explains there is a right way to start using monorepos in both situations.   Asking the important question is how to get started. Agreeing upon the structure, naming, ownership, are you going to build the frontend and backend in the same repo, and the answers to a bunch of other questions will affect your work the most, even more than the tooling you use. Some of these answers will be specific to your company where others will be universal, like naming and ownership.    With other tools for monorepo out there, the panel asks Victor why Nrwl decided to build their own tool. Victor explains that the current tools on the market do not do it all. Lerna only does one thing great and Bazel is very selective on who can run it. Nrwl is hoping to marry Bazel to Nx, so they can allow everyone to use Bazel. They want Nx to support all tools and even Windows.    The panel wonders if Nx is perfect. Victor explains that it nearly there. Nx is pluggable and easy to use. It is easy to learn. Victor explains that they really care about developer experience at Nrwl. Nx is free and opensource so everyone can give monorepos a try.    Resources for learning about monorepos are discussed. Victor invites everyone to watch the ten-minute getting started video on the Nx website. He also lets the listeners know about a new book coming out mid-September and it will be more organizational based than the last. The panel wants to know what comes with Nx. Victor explains that Nx gives you modern tools by setting up Cypress, Jest and other tools for you.   Because Nrwl is a consulting firm, the panel hopes that Victor will have an update on the trends. Victor shares his view that trends don’t really tell you anything about the true status of a framework. How many downloads a framework has doesn’t show the longevity of that framework. Frameworks being used to make large scale apps that will be around for years is how you can tell the longevity of a framework. From that perspective, Victor feels that Angular is doing really well.    To end the episode, Shai Reznik recalls how passionate Victor was about NgRx a few years ago. He asks Victor if he still feels the same way as before. Victor explains that NgRx is pretty well most of the time, has great docs, is well maintained, and he would still recommend it. Panelists Jennifer Wadella Brian Love Shai Reznik Alyssa Nicoll Guest Victor Savkin Sponsors   Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp My JavaScript Story Cachefly Links https://twitter.com/victorsavkin?lang=en Nrwl Nx — An open source toolkit for enterprise Angular applications. Effective React Development with Nx https://connect.nrwl.io/app/books https://nx.dev/angular/getting-started/what-is-nx MAS 040: Victor Savkin 042 AiA Dependency Injection and Change Detection with Victor Savkin 123 AiA Upgrading from Angular 1 to Angular 2 with Victor Savkin https://nrwl.io/ https://nx.dev/ Momentum  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: https://trunkbaseddevelopment.com/ https://www.oreilly.com/library/view/why-angular-for/9781492030294/  Alyssa Nicoll: Caffeine Content Warning! Jennnifer Wadella: The Fall Season NGD Conf Laptop Safety at Conferences Victor Savkin: The Boys Use Less Social Media Freedom App Shai Reznik: https://bit.dev/  True Detective  

Episode Summary   Victor Savkin, former angular team member and now cofounder of Narwhal Technologies Inc or Nrwl, returns to Adventures in Angular to teach the panel about monorepos. Victor starts by explaining what monorepos are and why you might need one. Monorepo style development is when multiple projects developed in the same repository and the tools used to manage code between those apps.    There are many benefits to using monorepos as Victor explains to the panel, such as sharing code between apps. Monorepos help you see what's going on in reality as well as helps you take control of the structure of your code. It also allows for more interesting deployment strategies. Victor talks briefly about his time at Google, working on the toolchain and using a large monorepo.   After the panel asks about the costs of using a monorepo strategy, Victor explains that there are many perceived costs that are actually false or easily overcome. The first perceived cost he tells the panel about is how people get confused and believe that apps have to be deployed together when they really have to be developed in the same repository. The second is the fear of misplaced ownership, that some other developer will come along and ruin their code. Victor explains that ownership can be configured and controlled so that no one you don’t trust can touch your code.    The next myth developers believe about monorepos is that it doesn’t scale and especially when it comes to performance. Victor explains that when the app is set up correctly and testing used correctly this isn’t a problem. The final perceived cost is that Git will break. Victor debunks this by explaining that you would have to be doing extremely well in order for Git to be a bottleneck and even then there are ways around that problem.    Victor explains the one real cost and that is you have to change the way you code. The panel discusses a few different coding styles. Victor recommends getting used to single version policy and trunk-based development. He defines trunk-based development, explaining how it works and why it is better for monorepos than long-range branch development.    Victor sees two types of groups who want to get started in monorepos and he explains what they most commonly do wrong. The first is greenfield projects who jump right in without thinking about it and eventually crash. The second is teams with a giant app and through a monorepo in hoping it will help them structure their app. He explains there is a right way to start using monorepos in both situations.   Asking the important question is how to get started. Agreeing upon the structure, naming, ownership, are you going to build the frontend and backend in the same repo, and the answers to a bunch of other questions will affect your work the most, even more than the tooling you use. Some of these answers will be specific to your company where others will be universal, like naming and ownership.    With other tools for monorepo out there, the panel asks Victor why Nrwl decided to build their own tool. Victor explains that the current tools on the market do not do it all. Lerna only does one thing great and Bazel is very selective on who can run it. Nrwl is hoping to marry Bazel to Nx, so they can allow everyone to use Bazel. They want Nx to support all tools and even Windows.    The panel wonders if Nx is perfect. Victor explains that it nearly there. Nx is pluggable and easy to use. It is easy to learn. Victor explains that they really care about developer experience at Nrwl. Nx is free and opensource so everyone can give monorepos a try.    Resources for learning about monorepos are discussed. Victor invites everyone to watch the ten-minute getting started video on the Nx website. He also lets the listeners know about a new book coming out mid-September and it will be more organizational based than the last. The panel wants to know what comes with Nx. Victor explains that Nx gives you modern tools by setting up Cypress, Jest and other tools for you.   Because Nrwl is a consulting firm, the panel hopes that Victor will have an update on the trends. Victor shares his view that trends don’t really tell you anything about the true status of a framework. How many downloads a framework has doesn’t show the longevity of that framework. Frameworks being used to make large scale apps that will be around for years is how you can tell the longevity of a framework. From that perspective, Victor feels that Angular is doing really well.    To end the episode, Shai Reznik recalls how passionate Victor was about NgRx a few years ago. He asks Victor if he still feels the same way as before. Victor explains that NgRx is pretty well most of the time, has great docs, is well maintained, and he would still recommend it. Panelists Jennifer Wadella Brian Love Shai Reznik Alyssa Nicoll Guest Victor Savkin Sponsors   Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp My JavaScript Story Cachefly Links https://twitter.com/victorsavkin?lang=en Nrwl Nx — An open source toolkit for enterprise Angular applications. Effective React Development with Nx https://connect.nrwl.io/app/books https://nx.dev/angular/getting-started/what-is-nx MAS 040: Victor Savkin 042 AiA Dependency Injection and Change Detection with Victor Savkin 123 AiA Upgrading from Angular 1 to Angular 2 with Victor Savkin https://nrwl.io/ https://nx.dev/ Momentum  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: https://trunkbaseddevelopment.com/ https://www.oreilly.com/library/view/why-angular-for/9781492030294/  Alyssa Nicoll: Caffeine Content Warning! Jennnifer Wadella: The Fall Season NGD Conf Laptop Safety at Conferences Victor Savkin: The Boys Use Less Social Media Freedom App Shai Reznik: https://bit.dev/  True Detective  

Episode Summary   Victor Savkin, former angular team member and now cofounder of Narwhal Technologies Inc or Nrwl, returns to Adventures in Angular to teach the panel about monorepos. Victor starts by explaining what monorepos are and why you might need one. Monorepo style development is when multiple projects developed in the same repository and the tools used to manage code between those apps.    There are many benefits to using monorepos as Victor explains to the panel, such as sharing code between apps. Monorepos help you see what's going on in reality as well as helps you take control of the structure of your code. It also allows for more interesting deployment strategies. Victor talks briefly about his time at Google, working on the toolchain and using a large monorepo.   After the panel asks about the costs of using a monorepo strategy, Victor explains that there are many perceived costs that are actually false or easily overcome. The first perceived cost he tells the panel about is how people get confused and believe that apps have to be deployed together when they really have to be developed in the same repository. The second is the fear of misplaced ownership, that some other developer will come along and ruin their code. Victor explains that ownership can be configured and controlled so that no one you don’t trust can touch your code.    The next myth developers believe about monorepos is that it doesn’t scale and especially when it comes to performance. Victor explains that when the app is set up correctly and testing used correctly this isn’t a problem. The final perceived cost is that Git will break. Victor debunks this by explaining that you would have to be doing extremely well in order for Git to be a bottleneck and even then there are ways around that problem.    Victor explains the one real cost and that is you have to change the way you code. The panel discusses a few different coding styles. Victor recommends getting used to single version policy and trunk-based development. He defines trunk-based development, explaining how it works and why it is better for monorepos than long-range branch development.    Victor sees two types of groups who want to get started in monorepos and he explains what they most commonly do wrong. The first is greenfield projects who jump right in without thinking about it and eventually crash. The second is teams with a giant app and through a monorepo in hoping it will help them structure their app. He explains there is a right way to start using monorepos in both situations.   Asking the important question is how to get started. Agreeing upon the structure, naming, ownership, are you going to build the frontend and backend in the same repo, and the answers to a bunch of other questions will affect your work the most, even more than the tooling you use. Some of these answers will be specific to your company where others will be universal, like naming and ownership.    With other tools for monorepo out there, the panel asks Victor why Nrwl decided to build their own tool. Victor explains that the current tools on the market do not do it all. Lerna only does one thing great and Bazel is very selective on who can run it. Nrwl is hoping to marry Bazel to Nx, so they can allow everyone to use Bazel. They want Nx to support all tools and even Windows.    The panel wonders if Nx is perfect. Victor explains that it nearly there. Nx is pluggable and easy to use. It is easy to learn. Victor explains that they really care about developer experience at Nrwl. Nx is free and opensource so everyone can give monorepos a try.    Resources for learning about monorepos are discussed. Victor invites everyone to watch the ten-minute getting started video on the Nx website. He also lets the listeners know about a new book coming out mid-September and it will be more organizational based than the last. The panel wants to know what comes with Nx. Victor explains that Nx gives you modern tools by setting up Cypress, Jest and other tools for you.   Because Nrwl is a consulting firm, the panel hopes that Victor will have an update on the trends. Victor shares his view that trends don’t really tell you anything about the true status of a framework. How many downloads a framework has doesn’t show the longevity of that framework. Frameworks being used to make large scale apps that will be around for years is how you can tell the longevity of a framework. From that perspective, Victor feels that Angular is doing really well.    To end the episode, Shai Reznik recalls how passionate Victor was about NgRx a few years ago. He asks Victor if he still feels the same way as before. Victor explains that NgRx is pretty well most of the time, has great docs, is well maintained, and he would still recommend it. Panelists Jennifer Wadella Brian Love Shai Reznik Alyssa Nicoll Guest Victor Savkin Sponsors   Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp My JavaScript Story Cachefly Links https://twitter.com/victorsavkin?lang=en Nrwl Nx — An open source toolkit for enterprise Angular applications. Effective React Development with Nx https://connect.nrwl.io/app/books https://nx.dev/angular/getting-started/what-is-nx MAS 040: Victor Savkin 042 AiA Dependency Injection and Change Detection with Victor Savkin 123 AiA Upgrading from Angular 1 to Angular 2 with Victor Savkin https://nrwl.io/ https://nx.dev/ Momentum  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: https://trunkbaseddevelopment.com/ https://www.oreilly.com/library/view/why-angular-for/9781492030294/  Alyssa Nicoll: Caffeine Content Warning! Jennnifer Wadella: The Fall Season NGD Conf Laptop Safety at Conferences Victor Savkin: The Boys Use Less Social Media Freedom App Shai Reznik: https://bit.dev/  True Detective  

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Adventures in Blockchain Cachefly Panel Jennifer Wadella Brian Love Aaron Frost Alyssa Nicoll Summary Addressing the recent twitter fire surrounding the JavaScript community, the panel shares their opinions on social awareness. They begin by discussing a time they inadvertently offended others and what they learned. They consider the best way to respond if you do offend someone; the correct way to apologize and learn from your mistake. The importance of taking responsibility and sharing a desire to learn is discussed.    The panel considers how the community can be proactive in creating a safe space while being inclusive of everyone. They discuss resources for learning about sexism, racism and not feeling guilty as a victim. Links The Missing Stair The Gift of Fear https://twitter.com/TatianaTMac/status/1165781104122634240  https://twitter.com/why_is_js_mad/status/1164603312915791873 https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Aaron Frost: Family Time Brain Love: Disconnect and enjoy real life https://codeimg.io/  Alyssa Nicoll: Family time Jennnifer Wadella: Everyone Is In Love With These Fashionable Women On TikTok  Taylor Swift- Lover

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Adventures in Blockchain Cachefly Panel Jennifer Wadella Brian Love Aaron Frost Alyssa Nicoll Summary Addressing the recent twitter fire surrounding the JavaScript community, the panel shares their opinions on social awareness. They begin by discussing a time they inadvertently offended others and what they learned. They consider the best way to respond if you do offend someone; the correct way to apologize and learn from your mistake. The importance of taking responsibility and sharing a desire to learn is discussed.    The panel considers how the community can be proactive in creating a safe space while being inclusive of everyone. They discuss resources for learning about sexism, racism and not feeling guilty as a victim. Links The Missing Stair The Gift of Fear https://twitter.com/TatianaTMac/status/1165781104122634240  https://twitter.com/why_is_js_mad/status/1164603312915791873 https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Aaron Frost: Family Time Brain Love: Disconnect and enjoy real life https://codeimg.io/  Alyssa Nicoll: Family time Jennnifer Wadella: Everyone Is In Love With These Fashionable Women On TikTok  Taylor Swift- Lover

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Adventures in Blockchain Cachefly Panel Jennifer Wadella Brian Love Aaron Frost Alyssa Nicoll Summary Addressing the recent twitter fire surrounding the JavaScript community, the panel shares their opinions on social awareness. They begin by discussing a time they inadvertently offended others and what they learned. They consider the best way to respond if you do offend someone; the correct way to apologize and learn from your mistake. The importance of taking responsibility and sharing a desire to learn is discussed.    The panel considers how the community can be proactive in creating a safe space while being inclusive of everyone. They discuss resources for learning about sexism, racism and not feeling guilty as a victim. Links The Missing Stair The Gift of Fear https://twitter.com/TatianaTMac/status/1165781104122634240  https://twitter.com/why_is_js_mad/status/1164603312915791873 https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Aaron Frost: Family Time Brain Love: Disconnect and enjoy real life https://codeimg.io/  Alyssa Nicoll: Family time Jennnifer Wadella: Everyone Is In Love With These Fashionable Women On TikTok  Taylor Swift- Lover

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp iPhreaks Podcast CacheFly Panel Aaron Frost Joe Eames Alyssa Nicoll Joined By Special Guest: Brandon Roberts Episode Summary Joining the panel in this episode is Brandon Roberts, a Senior Angular Engineer at Narwhal Technologies. Brandon was previously on the Angular Team at Google. Brandon talks about what he is working on currently at Narwhal. They have recently launched more support for React and Web Components and Brandon talks about his role in that project. The panel then asks when Narwhal will release support for Knockout and jQuery. They talk about cases when to use Nx and when to use Angular CLI. They then talk about the effort required to learn Nx. They then talk about Narwhal's support plans for NgRx 9.   Links MAS 091: Brandon Roberts NgRx: A Reactive State of Mind (Two Day Workshop) https://www.ng-conf.org/2019/speakers/brandon-roberts/ Brandon Roberts – Medium Brandon (@brandontroberts) | Twitter Building Full-Stack Applications Using Angular CLI and Nx - Nrwl nrwl/nx: Extensible Dev Tools for Monorepos - GitHub   Picks Alyssa Nicoll: ngAir 211 - Template Streams in Angular & Change Detection Profiling w/ Dominic Elm & Kwinten Pisman Joe Eames: Roll for Adventure Board Game Stop Thief! Board Game Aaron Frost: Your local swap meet MLS Soccer Utah Jazz Brandon Roberts: Connect Tech NWA Technology Summit 2019

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp iPhreaks Podcast CacheFly Panel Aaron Frost Joe Eames Alyssa Nicoll Joined By Special Guest: Brandon Roberts Episode Summary Joining the panel in this episode is Brandon Roberts, a Senior Angular Engineer at Narwhal Technologies. Brandon was previously on the Angular Team at Google. Brandon talks about what he is working on currently at Narwhal. They have recently launched more support for React and Web Components and Brandon talks about his role in that project. The panel then asks when Narwhal will release support for Knockout and jQuery. They talk about cases when to use Nx and when to use Angular CLI. They then talk about the effort required to learn Nx. They then talk about Narwhal's support plans for NgRx 9.   Links MAS 091: Brandon Roberts NgRx: A Reactive State of Mind (Two Day Workshop) https://www.ng-conf.org/2019/speakers/brandon-roberts/ Brandon Roberts – Medium Brandon (@brandontroberts) | Twitter Building Full-Stack Applications Using Angular CLI and Nx - Nrwl nrwl/nx: Extensible Dev Tools for Monorepos - GitHub   Picks Alyssa Nicoll: ngAir 211 - Template Streams in Angular & Change Detection Profiling w/ Dominic Elm & Kwinten Pisman Joe Eames: Roll for Adventure Board Game Stop Thief! Board Game Aaron Frost: Your local swap meet MLS Soccer Utah Jazz Brandon Roberts: Connect Tech NWA Technology Summit 2019

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp iPhreaks Podcast CacheFly Panel Aaron Frost Joe Eames Alyssa Nicoll Joined By Special Guest: Brandon Roberts Episode Summary Joining the panel in this episode is Brandon Roberts, a Senior Angular Engineer at Narwhal Technologies. Brandon was previously on the Angular Team at Google. Brandon talks about what he is working on currently at Narwhal. They have recently launched more support for React and Web Components and Brandon talks about his role in that project. The panel then asks when Narwhal will release support for Knockout and jQuery. They talk about cases when to use Nx and when to use Angular CLI. They then talk about the effort required to learn Nx. They then talk about Narwhal's support plans for NgRx 9.   Links MAS 091: Brandon Roberts NgRx: A Reactive State of Mind (Two Day Workshop) https://www.ng-conf.org/2019/speakers/brandon-roberts/ Brandon Roberts – Medium Brandon (@brandontroberts) | Twitter Building Full-Stack Applications Using Angular CLI and Nx - Nrwl nrwl/nx: Extensible Dev Tools for Monorepos - GitHub   Picks Alyssa Nicoll: ngAir 211 - Template Streams in Angular & Change Detection Profiling w/ Dominic Elm & Kwinten Pisman Joe Eames: Roll for Adventure Board Game Stop Thief! Board Game Aaron Frost: Your local swap meet MLS Soccer Utah Jazz Brandon Roberts: Connect Tech NWA Technology Summit 2019

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Shai Reznik Joined By Special Guest: Hans Larsen Episode Summary Hans Larsen, Team Lead of the Angular CLI at Google has left Google to pursue other opportunities. The panel meets with Hans to talk out about his time at Google Angular team and some of the challenges they faced. They then talk about Hans' future plans as well as some of the fun times they had at the Angular conferences. Links Hans Larsen LinkedIn Hans (@hanslatwork) | Twitter Angular is About Love! webpack Picks Shai Reznik: 16 Personalities Aaron Frost: NOVA: Black Hole Apocalypse | Netflix Hans Larsen: Become a parent Have a drink with someone you love

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Shai Reznik Joined By Special Guest: Hans Larsen Episode Summary Hans Larsen, Team Lead of the Angular CLI at Google has left Google to pursue other opportunities. The panel meets with Hans to talk out about his time at Google Angular team and some of the challenges they faced. They then talk about Hans' future plans as well as some of the fun times they had at the Angular conferences. Links Hans Larsen LinkedIn Hans (@hanslatwork) | Twitter Angular is About Love! webpack Picks Shai Reznik: 16 Personalities Aaron Frost: NOVA: Black Hole Apocalypse | Netflix Hans Larsen: Become a parent Have a drink with someone you love

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Shai Reznik Joined By Special Guest: Hans Larsen Episode Summary Hans Larsen, Team Lead of the Angular CLI at Google has left Google to pursue other opportunities. The panel meets with Hans to talk out about his time at Google Angular team and some of the challenges they faced. They then talk about Hans' future plans as well as some of the fun times they had at the Angular conferences. Links Hans Larsen LinkedIn Hans (@hanslatwork) | Twitter Angular is About Love! webpack Picks Shai Reznik: 16 Personalities Aaron Frost: NOVA: Black Hole Apocalypse | Netflix Hans Larsen: Become a parent Have a drink with someone you love

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Alyssa Nicoll Shai Reznik Joined By Special Guest: Craig Spence Episode Summary Craig Spence was a developer at Trade Me in New Zealand before he moved to Sweden to join Spotify. Trade Me is New Zealand's biggest website and it is similar to eBay where people buy and sell lots of different items. Craig talks about his experiences migrating Trade Me from AngularJS to Angular and the challenges they faced. One of the tips Craig has for the audience is when faced with a problem it is better to ask for help from those who have been in similar situations before, rather that attempting to solve it alone. The panel also agrees that developers should stop writing in AngularJS and make the decision to move forward. Craig recently started working at Spotify in Sweden and is dealing with a challenging bug that has lasted for over 13 days. Links Craig's LinkedIn Craig's Twitter Trade Me Spotify Angular Denver Picks Aaron Frost: OnePlus 7 Pro Chloe Condon - NG-Conf Alyssa Nicoll: Angular Denver Shai Reznik: https://github.com/hirezio/jasmine-auto-spies Craig Spence: Frank Turner

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Alyssa Nicoll Shai Reznik Joined By Special Guest: Craig Spence Episode Summary Craig Spence was a developer at Trade Me in New Zealand before he moved to Sweden to join Spotify. Trade Me is New Zealand's biggest website and it is similar to eBay where people buy and sell lots of different items. Craig talks about his experiences migrating Trade Me from AngularJS to Angular and the challenges they faced. One of the tips Craig has for the audience is when faced with a problem it is better to ask for help from those who have been in similar situations before, rather that attempting to solve it alone. The panel also agrees that developers should stop writing in AngularJS and make the decision to move forward. Craig recently started working at Spotify in Sweden and is dealing with a challenging bug that has lasted for over 13 days. Links Craig's LinkedIn Craig's Twitter Trade Me Spotify Angular Denver Picks Aaron Frost: OnePlus 7 Pro Chloe Condon - NG-Conf Alyssa Nicoll: Angular Denver Shai Reznik: https://github.com/hirezio/jasmine-auto-spies Craig Spence: Frank Turner

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Alyssa Nicoll Shai Reznik Joined By Special Guest: Craig Spence Episode Summary Craig Spence was a developer at Trade Me in New Zealand before he moved to Sweden to join Spotify. Trade Me is New Zealand's biggest website and it is similar to eBay where people buy and sell lots of different items. Craig talks about his experiences migrating Trade Me from AngularJS to Angular and the challenges they faced. One of the tips Craig has for the audience is when faced with a problem it is better to ask for help from those who have been in similar situations before, rather that attempting to solve it alone. The panel also agrees that developers should stop writing in AngularJS and make the decision to move forward. Craig recently started working at Spotify in Sweden and is dealing with a challenging bug that has lasted for over 13 days. Links Craig's LinkedIn Craig's Twitter Trade Me Spotify Angular Denver Picks Aaron Frost: OnePlus 7 Pro Chloe Condon - NG-Conf Alyssa Nicoll: Angular Denver Shai Reznik: https://github.com/hirezio/jasmine-auto-spies Craig Spence: Frank Turner

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Joe Eames Shai Reznik Jennifer Wadella Episode Summary Much reaction has been received for the tweet about the 10x developers and this week the panel outlines the checklist a 10x developer has to meet in order to be considered a 10x developer (a developer that outputs 10 times more code than the rest of the company). From always having their screen background set to black to their generally toxic attitude that is disliked by the rest of the team, 10x developers are generally a reason for others to quit their job. The panel discusses why managers continue to keep these people on even though they affect the overall team production negatively and how they should be dealt with. Links https://twitter.com/skirani/status/1149302834619248640 https://twitter.com/mike_conley/status/1149851483241947137 Picks Shai Reznik: PubConf Jennifer Wadella: PubConf The Bachelorette Joe Eames: Emotional IQ Aaron Frost: OnePlus 7 Pro Observables Pablo Fransisco Bits and Pieces

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Joe Eames Shai Reznik Jennifer Wadella Episode Summary Much reaction has been received for the tweet about the 10x developers and this week the panel outlines the checklist a 10x developer has to meet in order to be considered a 10x developer (a developer that outputs 10 times more code than the rest of the company). From always having their screen background set to black to their generally toxic attitude that is disliked by the rest of the team, 10x developers are generally a reason for others to quit their job. The panel discusses why managers continue to keep these people on even though they affect the overall team production negatively and how they should be dealt with. Links https://twitter.com/skirani/status/1149302834619248640 https://twitter.com/mike_conley/status/1149851483241947137 Picks Shai Reznik: PubConf Jennifer Wadella: PubConf The Bachelorette Joe Eames: Emotional IQ Aaron Frost: OnePlus 7 Pro Observables Pablo Fransisco Bits and Pieces

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Joe Eames Shai Reznik Jennifer Wadella Episode Summary Much reaction has been received for the tweet about the 10x developers and this week the panel outlines the checklist a 10x developer has to meet in order to be considered a 10x developer (a developer that outputs 10 times more code than the rest of the company). From always having their screen background set to black to their generally toxic attitude that is disliked by the rest of the team, 10x developers are generally a reason for others to quit their job. The panel discusses why managers continue to keep these people on even though they affect the overall team production negatively and how they should be dealt with. Links https://twitter.com/skirani/status/1149302834619248640 https://twitter.com/mike_conley/status/1149851483241947137 Picks Shai Reznik: PubConf Jennifer Wadella: PubConf The Bachelorette Joe Eames: Emotional IQ Aaron Frost: OnePlus 7 Pro Observables Pablo Fransisco Bits and Pieces

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Alyssa Nicoll Shai Reznik Joe Eames Brian Love Joined by Special Guest: Minko Gechev Episode Summary Minko from Angular team at Google talks about what's new in Angular v8 and what has changed. Some of the exciting new features include differential loading, dynamic imports for lazy routes and CLI workflow improvements which end up being a large perfomance improvement. The panel comments on the fact that it was effortless to migrate from Angular 7 to Angular 8, and Minko also mentions that they had received feedback that the how to start tutorials were not very clear and so in Angular v8 they made an effort to re-do the tutorials. Links Angular Versioning and Releases - Angular Minko's Twitter Minko's Blog Minko's GitHub https://caniuse.com/#search=modules Picks Aaron Frost: Stranger Things Season 3 Angular Denver Joe Eames: Bonnie Brennan and her daughter Sam Shai Reznik: Dev Ed Podcast: Making Learning Fun Ozark Cobra Kai Getting Out of Your Comfort Zone Alyssa Nicoll: ngAir 211 - Template Streams in Angular & Change Detection Profiling w/ Dominic Elm & Kwinten Pisman Brian Love: https://github.com/cartant/rxjs-spy Go Outside and Hike Minko Gechev: You can use the "safe navigation" operator in Angular templates Hit Fit SF

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Alyssa Nicoll Shai Reznik Joe Eames Brian Love Joined by Special Guest: Minko Gechev Episode Summary Minko from Angular team at Google talks about what's new in Angular v8 and what has changed. Some of the exciting new features include differential loading, dynamic imports for lazy routes and CLI workflow improvements which end up being a large perfomance improvement. The panel comments on the fact that it was effortless to migrate from Angular 7 to Angular 8, and Minko also mentions that they had received feedback that the how to start tutorials were not very clear and so in Angular v8 they made an effort to re-do the tutorials. Links Angular Versioning and Releases - Angular Minko's Twitter Minko's Blog Minko's GitHub https://caniuse.com/#search=modules Picks Aaron Frost: Stranger Things Season 3 Angular Denver Joe Eames: Bonnie Brennan and her daughter Sam Shai Reznik: Dev Ed Podcast: Making Learning Fun Ozark Cobra Kai Getting Out of Your Comfort Zone Alyssa Nicoll: ngAir 211 - Template Streams in Angular & Change Detection Profiling w/ Dominic Elm & Kwinten Pisman Brian Love: https://github.com/cartant/rxjs-spy Go Outside and Hike Minko Gechev: You can use the "safe navigation" operator in Angular templates Hit Fit SF

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Alyssa Nicoll Shai Reznik Joe Eames Brian Love Joined by Special Guest: Minko Gechev Episode Summary Minko from Angular team at Google talks about what's new in Angular v8 and what has changed. Some of the exciting new features include differential loading, dynamic imports for lazy routes and CLI workflow improvements which end up being a large perfomance improvement. The panel comments on the fact that it was effortless to migrate from Angular 7 to Angular 8, and Minko also mentions that they had received feedback that the how to start tutorials were not very clear and so in Angular v8 they made an effort to re-do the tutorials. Links Angular Versioning and Releases - Angular Minko's Twitter Minko's Blog Minko's GitHub https://caniuse.com/#search=modules Picks Aaron Frost: Stranger Things Season 3 Angular Denver Joe Eames: Bonnie Brennan and her daughter Sam Shai Reznik: Dev Ed Podcast: Making Learning Fun Ozark Cobra Kai Getting Out of Your Comfort Zone Alyssa Nicoll: ngAir 211 - Template Streams in Angular & Change Detection Profiling w/ Dominic Elm & Kwinten Pisman Brian Love: https://github.com/cartant/rxjs-spy Go Outside and Hike Minko Gechev: You can use the "safe navigation" operator in Angular templates Hit Fit SF

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Joe Eames Jennifer Wadella Brian Love Alyssa Nicoll Joined by Special Guest: Leonardo Zizzamia Episode Summary Leonardo is a Senior Software Engineer, Technical Lead at Coinbase a digital currency exchange headquartered in San Francisco. Leonardo and the panel talk about Perfume.js. Over the past 5 years the Chrome team has been working on standardizing user timings for the web. One of the most recent metric tool the Chrome team has built is the Performance Observer which is an experimental API that observes user metrics. Leonardo explains how Perfume.js helps users so they don't have to worry about not complying with web standards in terms of user metrics. Leonardo then gives some guidelines to the web standards and explains what is considered in the normal range and what needs to be improved. Links Leonardo's Twitter Coinbase CryptoKitties Okurrr2svg Perfume.js Spill The Tea- definition D&Diesel Picks Aaron Frost: Potion of Flying https://www.rxjs.live/ Joe Eames: Being a Guide and Not Being a Leader Jennifer Wadella: The Git Up by Blanco Brown Brian Love: https://github.com/tibing/async-pipeline Alyssa Nicoll: https://www.anxietytech.com/ Leonardo Zizzamia: https://ngrome.io/home https://devfestlevante.eu/

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Joe Eames Jennifer Wadella Brian Love Alyssa Nicoll Joined by Special Guest: Leonardo Zizzamia Episode Summary Leonardo is a Senior Software Engineer, Technical Lead at Coinbase a digital currency exchange headquartered in San Francisco. Leonardo and the panel talk about Perfume.js. Over the past 5 years the Chrome team has been working on standardizing user timings for the web. One of the most recent metric tool the Chrome team has built is the Performance Observer which is an experimental API that observes user metrics. Leonardo explains how Perfume.js helps users so they don't have to worry about not complying with web standards in terms of user metrics. Leonardo then gives some guidelines to the web standards and explains what is considered in the normal range and what needs to be improved. Links Leonardo's Twitter Coinbase CryptoKitties Okurrr2svg Perfume.js Spill The Tea- definition D&Diesel Picks Aaron Frost: Potion of Flying https://www.rxjs.live/ Joe Eames: Being a Guide and Not Being a Leader Jennifer Wadella: The Git Up by Blanco Brown Brian Love: https://github.com/tibing/async-pipeline Alyssa Nicoll: https://www.anxietytech.com/ Leonardo Zizzamia: https://ngrome.io/home https://devfestlevante.eu/

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp CacheFly Panel Aaron Frost Joe Eames Jennifer Wadella Brian Love Alyssa Nicoll Joined by Special Guest: Leonardo Zizzamia Episode Summary Leonardo is a Senior Software Engineer, Technical Lead at Coinbase a digital currency exchange headquartered in San Francisco. Leonardo and the panel talk about Perfume.js. Over the past 5 years the Chrome team has been working on standardizing user timings for the web. One of the most recent metric tool the Chrome team has built is the Performance Observer which is an experimental API that observes user metrics. Leonardo explains how Perfume.js helps users so they don't have to worry about not complying with web standards in terms of user metrics. Leonardo then gives some guidelines to the web standards and explains what is considered in the normal range and what needs to be improved. Links Leonardo's Twitter Coinbase CryptoKitties Okurrr2svg Perfume.js Spill The Tea- definition D&Diesel Picks Aaron Frost: Potion of Flying https://www.rxjs.live/ Joe Eames: Being a Guide and Not Being a Leader Jennifer Wadella: The Git Up by Blanco Brown Brian Love: https://github.com/tibing/async-pipeline Alyssa Nicoll: https://www.anxietytech.com/ Leonardo Zizzamia: https://ngrome.io/home https://devfestlevante.eu/

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Triplebyte offers a $1000 signing bonus CacheFly Panel Aaron Frost Joe Eames Jennifer Wadella Joined by Special Guest: Alex Eagle Episode Summary Alex Eagle is a Software Engineer on the core Angular team at Google. Alex and the panel talk about Bazel, a a free software tool that allows for the automation of building and testing of software. Links Alex’s GitHub Alex’s Twitter Alex’s LinkedIn Bazel Angular and Bazel Join BazelBuild on Slack! Picks Aaron Frost: Axe Throwing Jennifer Wadella: Drama on the The Bachelor ( TV series) Joe Eames: FIFA Women's World Cup France 2019 Playing Dungeons & Dragons with Aaron Frost Alex Eagle: Firefly (TV Series 2002–2003) - IMDb

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Triplebyte offers a $1000 signing bonus CacheFly Panel Aaron Frost Joe Eames Jennifer Wadella Joined by Special Guest: Alex Eagle Episode Summary Alex Eagle is a Software Engineer on the core Angular team at Google. Alex and the panel talk about Bazel, a a free software tool that allows for the automation of building and testing of software. Links Alex’s GitHub Alex’s Twitter Alex’s LinkedIn Bazel Angular and Bazel Join BazelBuild on Slack! Picks Aaron Frost: Axe Throwing Jennifer Wadella: Drama on the The Bachelor ( TV series) Joe Eames: FIFA Women's World Cup France 2019 Playing Dungeons & Dragons with Aaron Frost Alex Eagle: Firefly (TV Series 2002–2003) - IMDb

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Triplebyte offers a $1000 signing bonus CacheFly Panel Aaron Frost Joe Eames Jennifer Wadella Joined by Special Guest: Alex Eagle Episode Summary Alex Eagle is a Software Engineer on the core Angular team at Google. Alex and the panel talk about Bazel, a a free software tool that allows for the automation of building and testing of software. Links Alex’s GitHub Alex’s Twitter Alex’s LinkedIn Bazel Angular and Bazel Join BazelBuild on Slack! Picks Aaron Frost: Axe Throwing Jennifer Wadella: Drama on the The Bachelor ( TV series) Joe Eames: FIFA Women's World Cup France 2019 Playing Dungeons & Dragons with Aaron Frost Alex Eagle: Firefly (TV Series 2002–2003) - IMDb

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Triplebyte offers a $1000 signing bonus CacheFly Panel Aaron Frost Joe Eames Brian Love Joined by Special Guest: Michael Prentice Episode Summary Michael Prentice is the owner of DevIntent and an AngularJS Material Lead Maintainer at Rangle.io. Links Michael’s GitHub Michael’s Twitter Michael’s LinkedIn Picks Aaron Frost: rxjs.live Brian Love: Stephen Fluin - YouTube The Umbrella Academy Joe Eames: https://www.cypress.io/ Michael Prentice: Angular Hispano NG Bolivia 2019 NG Honduras 2019 ngSpain Frontend Masters

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Triplebyte offers a $1000 signing bonus CacheFly Panel Aaron Frost Joe Eames Brian Love Joined by Special Guest: Michael Prentice Episode Summary Michael Prentice is the owner of DevIntent and an AngularJS Material Lead Maintainer at Rangle.io. Links Michael’s GitHub Michael’s Twitter Michael’s LinkedIn Picks Aaron Frost: rxjs.live Brian Love: Stephen Fluin - YouTube The Umbrella Academy Joe Eames: https://www.cypress.io/ Michael Prentice: Angular Hispano NG Bolivia 2019 NG Honduras 2019 ngSpain Frontend Masters

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Triplebyte offers a $1000 signing bonus CacheFly Panel Aaron Frost Joe Eames Brian Love Joined by Special Guest: Michael Prentice Episode Summary Michael Prentice is the owner of DevIntent and an AngularJS Material Lead Maintainer at Rangle.io. Links Michael’s GitHub Michael’s Twitter Michael’s LinkedIn Picks Aaron Frost: rxjs.live Brian Love: Stephen Fluin - YouTube The Umbrella Academy Joe Eames: https://www.cypress.io/ Michael Prentice: Angular Hispano NG Bolivia 2019 NG Honduras 2019 ngSpain Frontend Masters

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Triplebyte offers a $1000 signing bonus CacheFly Panel Charles Max Wood Joined by Special Guest: Steve Faulkner Episode Summary Coming to you live from the podcast booth at Microsoft BUILD is Charles Max Wood with Steve Faulkner. Steve is a Senior Software Developer for Azure Cosmos DB at Microsoft. Cosmos DB is a global distributed, multi-model noSQL database. Steve explains the Cosmos DB service and scenarios it can be used in. They discuss how Cosmos DB interacts with Azure functions and how partition keys work in Cosmos DB. Listen to the show for more Cosmos DB updates and to find out how Steve he got his twitter handle @southpolesteve. Links Steve’s GitHub Steve’s Twitter Steve’s LinkedIn Steve Dev.to Microsoft Build 2019   Introduction to Azure Cosmos DB AiA 241: Azure Functions with Colby Tresness LIVE at Microsoft BUILD AiA 242- Azure Functions Part II with Jeff Hollan LIVE at Microsoft BUILD Microsoft Learn Resource Partitioning in Azure Cosmos DB Follow Adventures in Angular on tv, Facebook and Twitter. Picks Steve Faulkner: FINAL FANTASY X/X-2 HD Remaster for Nintendo Switch Overcooked on Steam Fastly