Podcast appearances and mentions of manfred steyer

Welcome to the Angular Master Podcast! I'm Dariusz Kalbarczyk, co-founder of NG Poland, JS Poland, AngularMaster.dev & WorkshopFest.dev, and in this episode, I'm thrilled to have the brilliant Manfred Steyer join me.

EPISODE DESCRIPTION:You really can't dive into learning Angular without coming across some kind of content from Manfred Steyer. He's about as synonymous with the framework as an individual can be. In this Dev Life edition of the Angular Plus Show, we sit down with Manfred to learn more about his developer journey, going from professor to trainer, a GDE, and an important external contributor to the Angular team itself. Manfred shares his unique insights on mastering the Angular framework, advancing in your career, and shares advice on public speaking and becoming an Angular GDE. Get ready for some major inspiration! This is… The Dev Life!LINKS:https://twitter.com/ManfredSteyerhttps://www.angulararchitects.io/Manfred's books on AmazonCONNECT WITH US:Manfred Steyer - @ManfredSteyerBrooke Avery - @jediBraveryPreston Lamb - @prestonjlamb

Hey, Angular fam!

John Papa @John_PapaWard Bell @WardBellDan Wahlin @DanWahlinCraig Shoemaker @craigshoemakerManfred Steyer @ManfredSteyerBrought to you byAG GridIdeaBladeResources:Angular Lazy loadingTo Decouple or Not to Decouple? The Answer Depends on Your Website (And Your Budget)Domain driven designBlog Series on Module Federation with AngularPiralFree eBook on Module Federation with AngularTimejumps00:37 Guest introduction01:11 How did you get started with micro front ends?03:36 What are the consequences of micro front ends?07:14 Why should someone use micro front ends?10:09 Sponsor: Ag Grid11:12 What are implementation details of working with micro front ends21:17 Sponsor: IdeaBlade22:13 Using hyperlinks to achieve micro front end28:29 How does a mobile device handle micro front ends?33:30 How do you get consistency across UX?35:38 Final thoughtsPodcast editing on this episode done by Chris Enns of Lemon Productions.

What's up everyone, this is Dariusz Kalbarczyk co-founder of NG Poland, JS Poland, AngularMaster.dev & WorkshopFest.dev. Welcome back to the Angular Master Podcast. Today, together with Manfred Steyer, who is an excellent Speaker, Trainer, Consultant and Author with focus on Angular. We will talk about Auth for SPAs and Micro Frontends You started a blog series where you tell us that the browser is no safe place for storing security tokens. However, it's quite modern to directly use JWT tokens, OAuth 2 and OpenId Connect in the browser. What's the reason for this? Do we need to panic, if we still use tokens in the browser? If we should not directly use security tokens in the browser, how to implement Single-Sign-on with existing identity solutions like Active Directory? How to deal with APIs of different origins? You also mention that there is a way to use these ideas to improve security while making everything easier. How is this even possible? Let's assume, we have installed and configured such a Security Gateway. What do I need to do on the client-side for authentication and authorization? And what do I need to do on the server-side? Can you tell us a bit about your reference implementation for this idea? You are using ASP.NET Core for this. What to do, if this is not part of our stack? What Identity Solutions does this implementation support? What's with Cross-Site-Request-Forgery Attacks, now, as we have cookies again? Do we need to protect ourselves from them? You also talked a lot about Micro Frontends recently. Does this approach also work with them or do we have to adjust it? --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

What's up everyone, this is Dariusz Kalbarczyk co-founder of NG Poland, JS Poland, AngularMaster.dev & WorkshopFest.dev. Welcome back to the Angular Master Podcast. Today, together with Manfred Steyer, who is an excellent speaker, trainer, consultant and author focusing on Angular. We will discuss in depth the new version of the Module Federation plugin for Angular. Topics discussed: - What's this plugin about? - Streamlined Configuration. - What's about shareAll? Is this dangerous? - Eager and Pinned Dependencies. - Dynamic Configuration and "Registry" Services. - Automatically Adding Secondary Entry Points. - run:all With Parameters. - What's the future of this plugin? --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

What's up everyone, this is Dariusz Kalbarczyk co-founder of NG Poland, JS Poland, AngularMaster.dev & WorkshopFest.dev. Welcome back to the Angular Master Podcast. Today, together with Manfred Steyer, who is an excellent Speaker, Trainer, Consultant and Author with focus on Angular. We will talk in depth about our video course Angular Architecture: Strategic Design with Nx, Edition 2022 https://angularmaster.dev --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

What's up everyone, this is Dariusz Kalbarczyk co-founder of NG Poland, JS Poland, AngularMaster.dev & WorkshopFest.dev. Welcome back to the Angular Master Podcast. Today, together with Manfred Steyer, who is an excellent Speaker, Trainer, Consultant and Author with focus on Angular. We will talk about Micro Frontends and Standalone Components You are doing quite a lot with Micro Frontends. However, there is the rumor that micro frontends are bad for UX and bundle sizes. Why's that? Well said. But if we decide to do so. How to deal with these problems? I have to ask this question. Does it really make sense to use Module Federation in Monorepo? Continuing the tone of the previous question. Are there technical reasons for introducing Module Federation? It is very interesting what you said. Let us go one step further. What are misconceptions you see in the area of Micro Frontends? How does the mental model behind the standalone components work? How to improve your architecture without NgModules? How to prepare for a NgModule-less world and how to migrate existing projects? How to use Standalone Components with existing code and Angular libs What are your wishes for the future of Micro Frontends? --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

What's up everyone, this is Dariusz Kalbarczyk co-founder of NG Poland, JS Poland, AngularMaster.dev & WorkshopFest.dev. Welcome back to the Angular Master Podcast. Today, together with Manfred Steyer, who is an excellent Speaker, Trainer, Consultant and Author with focus on Angular. We will talk about Standalone Components Link to book a place on the webinar: https://angularmaster.dev/webinars/ Originally, the idea was to not implement NgModules for Angular 2, as it was called back then. Why have they even been introduced in the first place? Why does the Angular team want to make them optional? How will working without NgModules look like? Isn't importing the whole context into Standalone Components exhausting? What's with existing source code and libs? Are Standalone Components compatible? Currently, the Angular Router uses NgModules, e. g. for lazy loading. How will this work in the future? What's with forRoot and forChild methods? Without NgModules, how can we structure our Angular applications in the future? --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

Manfred Steyer spricht über seine Karriere im Bereich Software-Architektur.

Nachdem es schon einige Folgen zum Thema Frontendarchitektur gab, die eher den Fokus auf Server-seitig gerenderte Architekturen gelegt haben, gibt es nun endlich eine Episode mit Manfred Steyer, die den Fokus auf Single Page Applications legt. Wir sprechen über Modularisierungskonzepte dieser Art von Architektur, wie zum Beispiel Microfrontends und Clients-Modulithen. Außerdem zeigen wir euch Entscheidungshilfen für die Wahl des passenden Konzepts und vieles mehr. Manfreds Blog

What's up everyone, this is Dariusz Kalbarczyk co-founder of NG Poland, JS Poland & AngularMaster.dev. Welcome back to Angular Master Podcast. Together with Manfred Steyer - Speaker, Trainer, Consultant, Author from angulararchitects.io. We discuss everything related to our favorite framework. Today we have some special guests from Dynatrace: Cornelia Rauch & Thomas Gsell. https://www.angulararchitects.io https://workshopfest.dev https://angularmaster.dev https://ng-poland.pl https://js-poland.pl --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

The eighth episode of the podcast is devoted to the broadly understood frontend technology, and in particular to our beloved Angular. Today our focus is on DDD. https://angularmaster.dev https://workshopfest.dev https://ng-poland.pl https://js-poland.pl Manfred Steyer https://www.angulararchitects.io Mira Manger https://www.gutfrau-softwaretechnik.de --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

The seventh episode of the podcast is devoted to the broadly understood frontend technology, and in particular to our beloved Angular. Today our focus is on DDD. https://angularmaster.dev https://ng-poland.pl https://js-poland.pl --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

The fifth episode of the podcast is devoted to the broadly understood front-end technology, in particular the beloved Angular. Today, my and your guest will be Manfred Steyer. Or rather, I should say, co-host, considering how many podcasts we recorded together! Today we are going to talk seriously about the Angular Security. 1. What is AuthGuard in Angular? 2. What is http interceptor in Angular? 3. Is Angular secure? 4. Token-based Security. What's it and why is it important? 5. Is JWT authentication or authorization? 6. Is JWT the same as OAuth? 7. Is it safe to store JWT in localStorage? 8. How do I verify my JWT? 9. Why use an Identity-as-a-Service-Solution like Auth0 instead of building your own user authentication from scratch? 10. OAuth2, how does this fit to Token-based Security? 11. What is the difference between OAuth and OAuth2? And a lot more! https://angularmaster.dev https://ng-poland.pl https://js-poland.pl --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

The third episode of the podcast is devoted to the broadly understood front-end technology, in particular the beloved Angular. Today we're focusing on Ivy. 1. What exactly is Ivy and what does it do differently than the previous Angular compiler? 2. What do we have to do, to use Ivy? 3. Ivy allows to shrink an Angular-based Hello World Application to just 14 KB. How is that possible? 4. What's with real-world-applications? 5. Ivy allows lazy loading of components? Why is this great and why hasn't this been possible before? 6. Are there any other things that Ivy enables? 7. How will optional NgModules work? 8. Zone-less Change Detection - why do we need Ivy for it? 9. How does Ivy enable meta programming and dynamic components? 10. Do we need to migrate to Ivy? And a lot more! https://angularmaster.dev https://ng-poland.pl https://js-poland.pl --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

The second episode of the podcast devoted to the broadly understood front-end technology, in particular to the beloved Angular. Manfred takes us on a journey through interesting, advanced aspects of Angular architecture. We are talking about Nx, NGRX, Micro Frontends, Monorepos and Security, among others. And finally a surprise topic ;) https://angularmaster.dev https://ng-poland.pl --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

The first episode of the podcast devoted to the broadly understood front-end technology, in particular to the beloved Angular. Manfred tells his story, about how he started his adventure with Angular and why he focused on architecture. https://angularmaster.dev https://ng-poland.pl --- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

John Papa @John_PapaWard Bell @WardBellDan Wahlin @DanWahlinCraig Shoemaker @craigshoemakerManfred Steyer @ManfredSteyerBrought to you byag-Grid RaygunActionable error, crash and performance monitoring. Raygun gives you visibility into how users are really experiencing your software. Detect, diagnose and resolve issues with greater speed and accuracy.Resources:Manfred's angular workshopsVS CodeVisual Studio Live ShareWhat is a monorepo?Nx toolsSelecting Monorepo tools.NET dotnetDesign Systems by Emma BostianAzure Static Web AppsMicro FrontendManfred Steyer video on Micro FrontendWebpack 5 and Module FederationConway’s law: in brief, s/w boundaries tend to mirror the development team boundariesMicro Frontends with Webpack Module Federation and AngularArchitecture with Angular and Nx MonoreposeBook about Enterprise AngularAngular Architecture WorkshopTimejumps01:12 Guest introductions04:39 What does enterprise mean to you?07:00 What are the pitfalls of mono repos?11:25 Why do I need special tooling?13:37 Sponsor: Raygun14:12 Tracking changes and version control30:22 Micro Front End concepts34:32 How do you link together multiple repos?36:00 Sponsor: Ag Grid37:03 Who is monorepo for?44:28 Final thoughtsPodcast editing on this episode done by Chris Enns of Lemon Productions.

Manfred Steyer stops by to educate us on what this whole micro front end movement is all about and explain the concept of module federation and the benefits we can realize from it in our Angular applications. Manfred on Twitter: https://twitter.com/manfredsteyer ----------------------------------------------- Angular Air is powered by StreamYard! It has been an amazing solution for our production pipeline. And it is 100% browser based. No app install needed! Want to host a live show with multiple guests? Check out StreamYard. https://streamyard.com/?pal=5070140888580096 --- Support this podcast: https://anchor.fm/angularair/support

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  

Manfred Steyer plaudert mit uns über Angular – das Thema, über das er zuvor bei unserem Meetup in Bad Nauheim sprach. Wieso Manfred sich bereits vor vielen Jahren Angular komplett hingegeben hat, erzählt er uns in dieser Folge. Außerdem sprechen wir über die Konzepte von Angular, welche Teile man für erfolgreiche Projekte benötigt und weitere Feinheiten wie Komponenten, Datenbindungen, Dependency Injection und der Einsatz von TypeScript. Auf seiner Webseite erfahrt ihr mehr über Manfred. Picks of the Day Fabi: Builder Pattern Manfred: Nx für Angular Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTube Erfahrt hier, wann das nächste Meetup in unserem Office in Bad Nauheim stattfindet. Meetup Musik: Hanimo

Panel: Charles Max Wood Joe Eames Aaron Frost Alyssa Nicoll Special Guests: Brian Love & Kevin Schuchard In this episode, the panelist talk with today’s special guests Brian Love & Kevin Schuchard! Brian and Kevin work at BrieBug – check out their employee profiles here! The panelist and guests talk about schematics, Angular, AST, and much more! Show Topics: 0:00 – Advertisement: Get A Coder Job! 0:50 – Chuck: Hello! Our panel today is Joe, Aaron, Alyssa, and myself. We have two guests today, and we are going to talk about schematics. Let’s dive into that! 1:46 – Guest: Schematics is a library that is coming out of Angular and the Angular Team. The guest gives a definition of Angular Schematics. 2:26 – Alyssa. 2:31 – Kevin: The functionality that you are hoping for depends on the CLI that you are on. 3:00 – Alyssa: Sorry for diving into the juicy stuff but we forgot to talk about your introductions! 3:19 – The guests talk about their backgrounds and introduce themselves to the panel and the listeners. 3:49 – Alyssa. 3:54 – Guest continues. 4:21 – Panel: Crazy and busy! 4:28 – Alyssa. 4:31 – Kevin: I am Senior Developer, and I have worked here for a few years. I have had the opportunities to write some schematics for the company and some of my own schematics. 4:53 – Alyssa: Aren’t you so proud that you are a “Senior Developer”?! 5:10 – Guest and panelists go back-and-forth. 6:23 – Guests: We want people to be familiar with schematics and start their journey with schematics. 6:50 – Panel: It’s kind of trippy isn’t that right? 7:00 – Guest: Yeah there are hurdles to learning schematics at first – for sure. 7:22 – Alyssa: What is AST? 7:29 – Guest gives a definition of AST and goes into much detail about this. 10:00 – Alyssa: I think I understand, now, what AST is. Thanks. Alyssa asks the guests a question. 10:14 – Guest answers the question about AST. 10:51 – Guest continues. 11:27 – Panelist is talking about the AST and schematics. 12:03 – Guest: You can read the whole file and using the AST you can figure out where you went to enter the text. 12:25 – Alyssa asks a question. 12:28 – Guest: We are not the developers of schematics, but we are just here to share our knowledge. I want to be super clear here. 13:39 – Panelist talks about schematics, CLI, and AST. 14:18 – Guest: You don’t have to know all about AST and everything there is to know to get into it. You can build schematics w/o getting into AST. Just to be clear. 14:39 – Alyssa asks a follow-up question. 14:41 – Guest continues. 15:57 – Guest: AST has been around for a while – it’s not a new thing it’s kind of an old thing. Guest talks about tools (Code Shift) that Facebook has built that is related to this topic. 17:22 – Guest: Yeah AST has been around for a while. 17:28 – Alyssa asks a question about Code Shift. 17:36 – Guest. 18:21 – Panel and guest go back-and-forth. 19:51 – Alyssa: You said you really don’t need to get into AST to do schematics – right? (Yes.) Alyssa asks a question. 20:19 – Guest: There are two pieces with schematics and that’s adding of new files and you can decide which pieces of the templates you want to be compiled. 21:58 – Chuck: For schematics you mentioned you could drop strings in. Chuck asks a question. 22:29 – Guest answers the question with a hypothetical situation. 23:09 – Chuck: I read the article you wrote and I have a question about your article. Tell me about the tree? 23:29 – Guest talks about the tree or aka the host. 25:40 – Guest: The tree is a virtual kind of context and it’s not committing all of the changes to the file system. Whether that is adding, deleting, or updating these files. 26:10 – Chuck: Makes sense to me. 26:15 – Guest continues talking about schematics. 26:53 – Alyssa: Yeoman is a replacement for schematics? 27:05 – Guest: It’s a lightweight alternative.  27:33 – Advertisement: Angular Boot Camp 28:10 – Chuck: How does one build a schematic? 28:16 – Guest answers the question. 30:34 – Panel: What’s the latest thing you’ve built? Talk about that, please. 30:40 – Guest: It’s a schematic and took what we’ve learned to set you up for a starter project. It starts with a blank project. 32:57 – Panel: You are just talking some lessons learned and you are saying this is how Kevin says to do it. You’ve packaged that up 33:26 – Guest: Yep I have found things that work and there isn’t any magic but put these practices together and made a repository to help testing and making schematics. 33:55 – Panel and guests go back-and-forth. 34:20 – Chuck: Let’s say I’ve built this schematic and Frosty wants to share it with his friends. How do we do that? How do you share it? Is there some component that you’ve built? 35:06 – Guest: It depends on what you are doing with it. 36:14 – Chuck: For mass production, though? 36:25 – Guest: I think Chuck is wondering about discoverability. Guest continues and he mentions prettier, extensions, among other things. 37:18 – Guest: I think it’s my favorite about schematics and it’s Kevin’s. 37:40 – Guest. 38:20 – Guest continues talking about schematics and ng-conf. 38:57 – Guest talks about libraries. 40:12 – Chuck: Anything else? Do you NPM install it and it’s just there? 40:29 – Guest: There are 2 ways to go about it. 53:05 – Fresh Books! END – CacheFly! Links: Vue jQuery Angular JavaScript Python React Cypress Yeoman Apache Groovy GitHub: prettier NG Conf Brian Love’s Website Kevin Schuchard’s LinkedIn BrieBug Blog Angular Schematics Tutorial Testing Schematics with a Sandbox + starter project GitHub: Schematic Starter Getting started blog post by Hans Schematics by Manfred Steyer Angular and Material CLI schematics 1 Angular and Material CLI schematics 2 AST Explorer Evening of Angular Example Schematic project with Sandbox: (Written by Kevin) https://github.com/briebug/jest-schematic https://github.com/schuchard/prettier-schematic https://github.com/briebug/ngrx-entity-schematic https://github.com/blove/schematics Sponsors: Angular Boot Camp Cache Fly Get A Coder Job Picks: Joe Brian Love BrieBug Schematics NGConf. Minified Aaron Ice Fishing Smoking Trout Joe Eames as Dungeon Master for DND NPM JS Survey Charles Alexa Briefing EntreProgrammers.com KanBanflow Pomodoro Technique Kevin Angular Material Open Source Projects Brian Angular.io Visits on Twitter Angular Community Jesse Sanders An evening of Angular Event

Panel: Charles Max Wood Joe Eames Aaron Frost Alyssa Nicoll Special Guests: Brian Love & Kevin Schuchard In this episode, the panelist talk with today’s special guests Brian Love & Kevin Schuchard! Brian and Kevin work at BrieBug – check out their employee profiles here! The panelist and guests talk about schematics, Angular, AST, and much more! Show Topics: 0:00 – Advertisement: Get A Coder Job! 0:50 – Chuck: Hello! Our panel today is Joe, Aaron, Alyssa, and myself. We have two guests today, and we are going to talk about schematics. Let’s dive into that! 1:46 – Guest: Schematics is a library that is coming out of Angular and the Angular Team. The guest gives a definition of Angular Schematics. 2:26 – Alyssa. 2:31 – Kevin: The functionality that you are hoping for depends on the CLI that you are on. 3:00 – Alyssa: Sorry for diving into the juicy stuff but we forgot to talk about your introductions! 3:19 – The guests talk about their backgrounds and introduce themselves to the panel and the listeners. 3:49 – Alyssa. 3:54 – Guest continues. 4:21 – Panel: Crazy and busy! 4:28 – Alyssa. 4:31 – Kevin: I am Senior Developer, and I have worked here for a few years. I have had the opportunities to write some schematics for the company and some of my own schematics. 4:53 – Alyssa: Aren’t you so proud that you are a “Senior Developer”?! 5:10 – Guest and panelists go back-and-forth. 6:23 – Guests: We want people to be familiar with schematics and start their journey with schematics. 6:50 – Panel: It’s kind of trippy isn’t that right? 7:00 – Guest: Yeah there are hurdles to learning schematics at first – for sure. 7:22 – Alyssa: What is AST? 7:29 – Guest gives a definition of AST and goes into much detail about this. 10:00 – Alyssa: I think I understand, now, what AST is. Thanks. Alyssa asks the guests a question. 10:14 – Guest answers the question about AST. 10:51 – Guest continues. 11:27 – Panelist is talking about the AST and schematics. 12:03 – Guest: You can read the whole file and using the AST you can figure out where you went to enter the text. 12:25 – Alyssa asks a question. 12:28 – Guest: We are not the developers of schematics, but we are just here to share our knowledge. I want to be super clear here. 13:39 – Panelist talks about schematics, CLI, and AST. 14:18 – Guest: You don’t have to know all about AST and everything there is to know to get into it. You can build schematics w/o getting into AST. Just to be clear. 14:39 – Alyssa asks a follow-up question. 14:41 – Guest continues. 15:57 – Guest: AST has been around for a while – it’s not a new thing it’s kind of an old thing. Guest talks about tools (Code Shift) that Facebook has built that is related to this topic. 17:22 – Guest: Yeah AST has been around for a while. 17:28 – Alyssa asks a question about Code Shift. 17:36 – Guest. 18:21 – Panel and guest go back-and-forth. 19:51 – Alyssa: You said you really don’t need to get into AST to do schematics – right? (Yes.) Alyssa asks a question. 20:19 – Guest: There are two pieces with schematics and that’s adding of new files and you can decide which pieces of the templates you want to be compiled. 21:58 – Chuck: For schematics you mentioned you could drop strings in. Chuck asks a question. 22:29 – Guest answers the question with a hypothetical situation. 23:09 – Chuck: I read the article you wrote and I have a question about your article. Tell me about the tree? 23:29 – Guest talks about the tree or aka the host. 25:40 – Guest: The tree is a virtual kind of context and it’s not committing all of the changes to the file system. Whether that is adding, deleting, or updating these files. 26:10 – Chuck: Makes sense to me. 26:15 – Guest continues talking about schematics. 26:53 – Alyssa: Yeoman is a replacement for schematics? 27:05 – Guest: It’s a lightweight alternative.  27:33 – Advertisement: Angular Boot Camp 28:10 – Chuck: How does one build a schematic? 28:16 – Guest answers the question. 30:34 – Panel: What’s the latest thing you’ve built? Talk about that, please. 30:40 – Guest: It’s a schematic and took what we’ve learned to set you up for a starter project. It starts with a blank project. 32:57 – Panel: You are just talking some lessons learned and you are saying this is how Kevin says to do it. You’ve packaged that up 33:26 – Guest: Yep I have found things that work and there isn’t any magic but put these practices together and made a repository to help testing and making schematics. 33:55 – Panel and guests go back-and-forth. 34:20 – Chuck: Let’s say I’ve built this schematic and Frosty wants to share it with his friends. How do we do that? How do you share it? Is there some component that you’ve built? 35:06 – Guest: It depends on what you are doing with it. 36:14 – Chuck: For mass production, though? 36:25 – Guest: I think Chuck is wondering about discoverability. Guest continues and he mentions prettier, extensions, among other things. 37:18 – Guest: I think it’s my favorite about schematics and it’s Kevin’s. 37:40 – Guest. 38:20 – Guest continues talking about schematics and ng-conf. 38:57 – Guest talks about libraries. 40:12 – Chuck: Anything else? Do you NPM install it and it’s just there? 40:29 – Guest: There are 2 ways to go about it. 53:05 – Fresh Books! END – CacheFly! Links: Vue jQuery Angular JavaScript Python React Cypress Yeoman Apache Groovy GitHub: prettier NG Conf Brian Love’s Website Kevin Schuchard’s LinkedIn BrieBug Blog Angular Schematics Tutorial Testing Schematics with a Sandbox + starter project GitHub: Schematic Starter Getting started blog post by Hans Schematics by Manfred Steyer Angular and Material CLI schematics 1 Angular and Material CLI schematics 2 AST Explorer Evening of Angular Example Schematic project with Sandbox: (Written by Kevin) https://github.com/briebug/jest-schematic https://github.com/schuchard/prettier-schematic https://github.com/briebug/ngrx-entity-schematic https://github.com/blove/schematics Sponsors: Angular Boot Camp Cache Fly Get A Coder Job Picks: Joe Brian Love BrieBug Schematics NGConf. Minified Aaron Ice Fishing Smoking Trout Joe Eames as Dungeon Master for DND NPM JS Survey Charles Alexa Briefing EntreProgrammers.com KanBanflow Pomodoro Technique Kevin Angular Material Open Source Projects Brian Angular.io Visits on Twitter Angular Community Jesse Sanders An evening of Angular Event

Panel: Charles Max Wood Joe Eames Aaron Frost Alyssa Nicoll Special Guests: Brian Love & Kevin Schuchard In this episode, the panelist talk with today’s special guests Brian Love & Kevin Schuchard! Brian and Kevin work at BrieBug – check out their employee profiles here! The panelist and guests talk about schematics, Angular, AST, and much more! Show Topics: 0:00 – Advertisement: Get A Coder Job! 0:50 – Chuck: Hello! Our panel today is Joe, Aaron, Alyssa, and myself. We have two guests today, and we are going to talk about schematics. Let’s dive into that! 1:46 – Guest: Schematics is a library that is coming out of Angular and the Angular Team. The guest gives a definition of Angular Schematics. 2:26 – Alyssa. 2:31 – Kevin: The functionality that you are hoping for depends on the CLI that you are on. 3:00 – Alyssa: Sorry for diving into the juicy stuff but we forgot to talk about your introductions! 3:19 – The guests talk about their backgrounds and introduce themselves to the panel and the listeners. 3:49 – Alyssa. 3:54 – Guest continues. 4:21 – Panel: Crazy and busy! 4:28 – Alyssa. 4:31 – Kevin: I am Senior Developer, and I have worked here for a few years. I have had the opportunities to write some schematics for the company and some of my own schematics. 4:53 – Alyssa: Aren’t you so proud that you are a “Senior Developer”?! 5:10 – Guest and panelists go back-and-forth. 6:23 – Guests: We want people to be familiar with schematics and start their journey with schematics. 6:50 – Panel: It’s kind of trippy isn’t that right? 7:00 – Guest: Yeah there are hurdles to learning schematics at first – for sure. 7:22 – Alyssa: What is AST? 7:29 – Guest gives a definition of AST and goes into much detail about this. 10:00 – Alyssa: I think I understand, now, what AST is. Thanks. Alyssa asks the guests a question. 10:14 – Guest answers the question about AST. 10:51 – Guest continues. 11:27 – Panelist is talking about the AST and schematics. 12:03 – Guest: You can read the whole file and using the AST you can figure out where you went to enter the text. 12:25 – Alyssa asks a question. 12:28 – Guest: We are not the developers of schematics, but we are just here to share our knowledge. I want to be super clear here. 13:39 – Panelist talks about schematics, CLI, and AST. 14:18 – Guest: You don’t have to know all about AST and everything there is to know to get into it. You can build schematics w/o getting into AST. Just to be clear. 14:39 – Alyssa asks a follow-up question. 14:41 – Guest continues. 15:57 – Guest: AST has been around for a while – it’s not a new thing it’s kind of an old thing. Guest talks about tools (Code Shift) that Facebook has built that is related to this topic. 17:22 – Guest: Yeah AST has been around for a while. 17:28 – Alyssa asks a question about Code Shift. 17:36 – Guest. 18:21 – Panel and guest go back-and-forth. 19:51 – Alyssa: You said you really don’t need to get into AST to do schematics – right? (Yes.) Alyssa asks a question. 20:19 – Guest: There are two pieces with schematics and that’s adding of new files and you can decide which pieces of the templates you want to be compiled. 21:58 – Chuck: For schematics you mentioned you could drop strings in. Chuck asks a question. 22:29 – Guest answers the question with a hypothetical situation. 23:09 – Chuck: I read the article you wrote and I have a question about your article. Tell me about the tree? 23:29 – Guest talks about the tree or aka the host. 25:40 – Guest: The tree is a virtual kind of context and it’s not committing all of the changes to the file system. Whether that is adding, deleting, or updating these files. 26:10 – Chuck: Makes sense to me. 26:15 – Guest continues talking about schematics. 26:53 – Alyssa: Yeoman is a replacement for schematics? 27:05 – Guest: It’s a lightweight alternative.  27:33 – Advertisement: Angular Boot Camp 28:10 – Chuck: How does one build a schematic? 28:16 – Guest answers the question. 30:34 – Panel: What’s the latest thing you’ve built? Talk about that, please. 30:40 – Guest: It’s a schematic and took what we’ve learned to set you up for a starter project. It starts with a blank project. 32:57 – Panel: You are just talking some lessons learned and you are saying this is how Kevin says to do it. You’ve packaged that up 33:26 – Guest: Yep I have found things that work and there isn’t any magic but put these practices together and made a repository to help testing and making schematics. 33:55 – Panel and guests go back-and-forth. 34:20 – Chuck: Let’s say I’ve built this schematic and Frosty wants to share it with his friends. How do we do that? How do you share it? Is there some component that you’ve built? 35:06 – Guest: It depends on what you are doing with it. 36:14 – Chuck: For mass production, though? 36:25 – Guest: I think Chuck is wondering about discoverability. Guest continues and he mentions prettier, extensions, among other things. 37:18 – Guest: I think it’s my favorite about schematics and it’s Kevin’s. 37:40 – Guest. 38:20 – Guest continues talking about schematics and ng-conf. 38:57 – Guest talks about libraries. 40:12 – Chuck: Anything else? Do you NPM install it and it’s just there? 40:29 – Guest: There are 2 ways to go about it. 53:05 – Fresh Books! END – CacheFly! Links: Vue jQuery Angular JavaScript Python React Cypress Yeoman Apache Groovy GitHub: prettier NG Conf Brian Love’s Website Kevin Schuchard’s LinkedIn BrieBug Blog Angular Schematics Tutorial Testing Schematics with a Sandbox + starter project GitHub: Schematic Starter Getting started blog post by Hans Schematics by Manfred Steyer Angular and Material CLI schematics 1 Angular and Material CLI schematics 2 AST Explorer Evening of Angular Example Schematic project with Sandbox: (Written by Kevin) https://github.com/briebug/jest-schematic https://github.com/schuchard/prettier-schematic https://github.com/briebug/ngrx-entity-schematic https://github.com/blove/schematics Sponsors: Angular Boot Camp Cache Fly Get A Coder Job Picks: Joe Brian Love BrieBug Schematics NGConf. Minified Aaron Ice Fishing Smoking Trout Joe Eames as Dungeon Master for DND NPM JS Survey Charles Alexa Briefing EntreProgrammers.com KanBanflow Pomodoro Technique Kevin Angular Material Open Source Projects Brian Angular.io Visits on Twitter Angular Community Jesse Sanders An evening of Angular Event

Panel:  Charles Max Wood Alyssa Nicoll Joe Eames Special Guests: Shmuela Jacobs In this episode of Adventures in Angular, the panel talks to Shmuela Jacobs about ngGirls. Shmuela founded ngGirls, which is an organization where they try to increase diversity in tech, and it is mainly focused towards Angular. This is because she loves Angular and feels that it is a good platform to start with because of its simplicity. They talk about how she came up with the idea for ngGirls, how the company works, and stress the incredibly helpful nature of the Angular community.  In particular, we dive pretty deep on: Shmuela intro Angular and ngGirls The Angular community How the workshop works Free workshop run by volunteers Going to be at Google I/O How did you come up with ngGirls? Django girls Women Who Code Great experience with Django girls Wanted a company geared towards Angular The tutorial was written by the community How much people in the Angular community want to help Angular JS Still so much to learn in Angular People taking over Workshops happen all over the world The company allows for other people to organize the workshops themselves Is ngGirls growing beyond you? Plans to start more with helping to guide others as the company grows Creating more activities for more experienced women or different ages And much, much more! Links:   ngGirls Angular Google I/O Django girls Angular JS @ShmuelaJ Shmuela’s GitHub Picks: Charles Google Drive ScanSnap S1300i Joe ngConf Role Playing Games Shmuela ngConf YouTube Super Powered, Server Rendered Progressive Native Apps - Nathan Walker & Jeff Whelpley Schematics: Generating custom Angular Code with the CLI by Manfred Steyer

Panel:  Charles Max Wood Alyssa Nicoll Joe Eames Special Guests: Shmuela Jacobs In this episode of Adventures in Angular, the panel talks to Shmuela Jacobs about ngGirls. Shmuela founded ngGirls, which is an organization where they try to increase diversity in tech, and it is mainly focused towards Angular. This is because she loves Angular and feels that it is a good platform to start with because of its simplicity. They talk about how she came up with the idea for ngGirls, how the company works, and stress the incredibly helpful nature of the Angular community.  In particular, we dive pretty deep on: Shmuela intro Angular and ngGirls The Angular community How the workshop works Free workshop run by volunteers Going to be at Google I/O How did you come up with ngGirls? Django girls Women Who Code Great experience with Django girls Wanted a company geared towards Angular The tutorial was written by the community How much people in the Angular community want to help Angular JS Still so much to learn in Angular People taking over Workshops happen all over the world The company allows for other people to organize the workshops themselves Is ngGirls growing beyond you? Plans to start more with helping to guide others as the company grows Creating more activities for more experienced women or different ages And much, much more! Links:   ngGirls Angular Google I/O Django girls Angular JS @ShmuelaJ Shmuela’s GitHub Picks: Charles Google Drive ScanSnap S1300i Joe ngConf Role Playing Games Shmuela ngConf YouTube Super Powered, Server Rendered Progressive Native Apps - Nathan Walker & Jeff Whelpley Schematics: Generating custom Angular Code with the CLI by Manfred Steyer

Panel:  Charles Max Wood Alyssa Nicoll Joe Eames Special Guests: Shmuela Jacobs In this episode of Adventures in Angular, the panel talks to Shmuela Jacobs about ngGirls. Shmuela founded ngGirls, which is an organization where they try to increase diversity in tech, and it is mainly focused towards Angular. This is because she loves Angular and feels that it is a good platform to start with because of its simplicity. They talk about how she came up with the idea for ngGirls, how the company works, and stress the incredibly helpful nature of the Angular community.  In particular, we dive pretty deep on: Shmuela intro Angular and ngGirls The Angular community How the workshop works Free workshop run by volunteers Going to be at Google I/O How did you come up with ngGirls? Django girls Women Who Code Great experience with Django girls Wanted a company geared towards Angular The tutorial was written by the community How much people in the Angular community want to help Angular JS Still so much to learn in Angular People taking over Workshops happen all over the world The company allows for other people to organize the workshops themselves Is ngGirls growing beyond you? Plans to start more with helping to guide others as the company grows Creating more activities for more experienced women or different ages And much, much more! Links:   ngGirls Angular Google I/O Django girls Angular JS @ShmuelaJ Shmuela’s GitHub Picks: Charles Google Drive ScanSnap S1300i Joe ngConf Role Playing Games Shmuela ngConf YouTube Super Powered, Server Rendered Progressive Native Apps - Nathan Walker & Jeff Whelpley Schematics: Generating custom Angular Code with the CLI by Manfred Steyer