Angular Architecture Podcast

Angular Schematics with Brian Love and Kevin Schuchard

In this episode, the Angularlicios podcast talks with two Angular Schematic experts. Brian Love, the CTO at Briebug Solutions, and Kevin Schuchard, a Senior Software Engineer at Briebug. Both Brian and Kevin have extensive experience with creating new Schematics, training, and using Schematics for Jest, Ngrx and for their clients.

This episode is a great introduction to what Angular Schematics are and how they can be used to improve developer workflow and productivity. It also covers:

* why developers should be interested in Schematics

* tools and packages

* how to develop and test in a sandbox

* adding 3rd-party libraries to projects (i.e., Jest, Cypress, Firebase, Prettier)

* resources to learn more about Schematics

Are you an effective Angular developer? Is your team effective? This episode looks at 3 Elements of Effectiveness. Learn how you and your team can improve in different areas.

We examine what is required to be effective in using our tools, continuous learning, and execution of our recipes, architecture, and process.

This episode is about some new tools for your Angular applications and development environments. Building custom libraries for your projects is not easy. However, there are some new tools that will improve your development environment by creating a consolidated workspace - so you can have multiple apps and libraries in the same environment.

And when you are all done you want to be able to show off all of your hard work. Using Stackblitz.io allows you to embed your project with code and a running application - all from your Github repository. That's pretty awesome.

The focus of this podcast is to identify software design patterns that are used in Angular with the goal of understanding how they work, why they are important. You will learn how to make services and components work better for you by knowing the patterns they implement.

Now that we have Typescript, you are armed with the ability to take advantage of Object Oriented Programming concepts and design patterns. You can use design patterns to produce better business logic. This episode provides some guidance on how to leverage these patterns. There are also some really useful code samples and templates on Github.com.

A podcast about things Angular, including architecture. This episode provides the background for this podcast and what you can expect from future episode.

The focus of this podcast is about how to use Angular Modules the right way. You'll discover how many modules your application really needs. Also, if you've ever wanted to create a custom Angular module to share and distribute - this podcast provides the information you'll need to create, publish, and use your custom module.

Free Guide: http://angularlicio.us/custom-angular-modules

The whole notion of modules is to create reusable items to improve efficiency and minimize maintenance of source code. The base element of an Angular application is a Module. Each Angular application contains an app.module that is the entry point of the entire application.

Therefore, you are already familiar with using modules. Also, it is very common to create additional modules in an Angular applications. However, what if you want to create Angular modules that can be reused in more than a single Angular application? Or, would you like to create custom modules that can be published to NPM and shared with the world?

Think of modules as containers of realted things. Even if you never create a custom module that is distributable, you can still dramatically improve the design of you existing Angular applications by creating modules to encapsulate and organize specific feature sets. Angular modules let you decide what items within the module are publicly available. For example, if you create a module that contains an Angular Service, it can act like an API that provides end-points to the application to perform different actions. You get to use and implement some nice architectural patterns that provide:

- A service facade pattern to provide end-points of functionality.

- Abstract the implementation details to private members of the module.

- Create a highly-testable service using specification tests.

Encapsulation of many items used to implement the feature set.