Podcast appearances and mentions of jeff whelpley

In this episode, Jeff Whelpley, Google Developer Expert in Angular, shares his expansive knowledge of Search Engine Optimization (SEO) with panelists Aaron Frost, Alyssa Nicol, Brian Love, and Jennifer Wadella. We talk about some of the basics of on-page optimizations such as Time to Interactive, First Meaningful Paint, etc. and the implications for Angular applications.Angular applications, in the context of the browser, are client-based and are built in the browser at runtime. While this provides many benefits to the user experience, it also comes with several challenges for SEO. Aaron and Jeff share some insight into these challenges, as well as the current solutions, including Scully for static prerendering and Angular Universal for server-side rendering.Finally, Jeff shares with us what Angular developers can do to optimize their applications for improved search engine result page rankings, including duplicated content, meta information, interlinking pages, crawl budgets, indexing, inbound links to leaf pages, and more.

In this episode of the DevEd podcast, David Graham - founder and CEO of Code Ninjas, introduces himself, gives a background of how he got into software development, briefly describes his vision that led to the creation of Code Ninjas and the interesting work that goes on there. The company essentially consists of coding centres for kids in multiple locations throughout the US, with cool learning programs catering to several age groups, its main purpose being teaching hands on software development combined with a lot of fun.  The panelists share their views about the current state of programming education in schools, if it is adequate, and what can be done to supplement it. They discuss that it is important to teach kids how to think and how to solve problems rather than relying on memory based learning. They mention ways to get students excited about programming, different learning tools and platforms, and similarities and differences in learning patterns between kids and adult learners.They talk on why should everyone care about coding education for kids, even those who do not have them, and how people can help out in getting youth involved in software development. They also discuss if there is anything they wish had existed to aid learning for young individuals also how it would help them in return. In the end, David explains how can people volunteer for Code Ninjas. Panel Brooke Avery Sam Julien Mike Dane Preston Lamb Joined by speacial guest: David Graham Sponsors Thinkster.io iPhreaks - Devchat.tv Views on Vue - Devchat.tv ________________________________________________________________________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood will be out on November 20th on Amazon.  Get your copy on that date only for $1. ________________________________________________________________________________________________________________________ Links Code Ninjas Code.org CodeCombat Picks Mike Dane: JBL Clip 3 David Graham: The Wheel of Time Preston Lamb: Disney+ Brooke Avery: Harry Potter Kano Coding Kit Sam Julien: Create Your Own Hacker Nebula with Angular Blockly by Jeff Whelpley & Madelyn Whelpley Blockly ng-club The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

In this episode of the DevEd podcast, David Graham - founder and CEO of Code Ninjas, introduces himself, gives a background of how he got into software development, briefly describes his vision that led to the creation of Code Ninjas and the interesting work that goes on there. The company essentially consists of coding centres for kids in multiple locations throughout the US, with cool learning programs catering to several age groups, its main purpose being teaching hands on software development combined with a lot of fun.  The panelists share their views about the current state of programming education in schools, if it is adequate, and what can be done to supplement it. They discuss that it is important to teach kids how to think and how to solve problems rather than relying on memory based learning. They mention ways to get students excited about programming, different learning tools and platforms, and similarities and differences in learning patterns between kids and adult learners.They talk on why should everyone care about coding education for kids, even those who do not have them, and how people can help out in getting youth involved in software development. They also discuss if there is anything they wish had existed to aid learning for young individuals also how it would help them in return. In the end, David explains how can people volunteer for Code Ninjas. Panel Brooke Avery Sam Julien Mike Dane Preston Lamb Joined by speacial guest: David Graham Sponsors Thinkster.io iPhreaks - Devchat.tv Views on Vue - Devchat.tv ________________________________________________________________________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood will be out on November 20th on Amazon.  Get your copy on that date only for $1. ________________________________________________________________________________________________________________________ Links Code Ninjas Code.org CodeCombat Picks Mike Dane: JBL Clip 3 David Graham: The Wheel of Time Preston Lamb: Disney+ Brooke Avery: Harry Potter Kano Coding Kit Sam Julien: Create Your Own Hacker Nebula with Angular Blockly by Jeff Whelpley & Madelyn Whelpley Blockly ng-club The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

Jeff Whelpley comes on the show to talk about Accelerated Mobile Pages (AMP) and how we can do it in our Angular apps. --- Video of episode: https://youtu.be/T_XpkInDUGg --- Support this podcast: https://anchor.fm/angularair/support

Jeff Whelpley joins us for a deep dive into Firestore --- Video of episode: https://youtu.be/jmitfq11FWA --- Support this podcast: https://anchor.fm/angularair/support

--- Support this podcast: https://anchor.fm/angularair/support

--- Support this podcast: https://anchor.fm/angularair/support

Ng-conf has happened! There were a bunch of excellent talks and and excellent people. Jeff Whelpley was one of them! Jeff helps us dive into what is coming in Angular. Angular 6, the new Angular CLI, RxJs 6 and more! There is a ton to unpack in this week's episode. Visit the website for This Week in Web, resources & more: https://thewebplatformpodcast.com/160-ngconf-2018   Follow The Web Platform podcast on Twitter for regular updates @TheWebPlatform.

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

Did you know there are basically four different budgeting techniques to use with the everyday money. They are: the cash envelope system, the survival budget, the balanced money formula and the budget burn down. If you’ve been a long-time listener, you know I am huge fan of the cash envelope system when you’re first getting started with forming a plan for your money. However, this doesn’t mean it’s a budgeting technique you have to develop and use forever. This week Jeff Whelpley, the co-founder of Swish, is coming on the show to talk about the BUDGET BURN DOWN technique - which may be a great fit for you. To give you a glimpse of how the burn down budget works, think of a fuel gauge on your car. Now, instead of gas and miles, think of money and life. If this doesn’t quite make sense yet --no worries. We will dive deep into the Budget Burn Down in this week’s episode. Here’s what you can expect from this week’s interview: Breakdown of the Cash Envelope System (still my favorite) Breakdown of the Survival Budget (best for the oh crap moments in life) Breakdown of the Balanced Money Formula (probably the most popular) Breakdown of the Budget Burn Down (maybe just what you’re looking for) How you can utilize the Budget Burn Down inside a free app All the show notes, the Swish app and anything Jeff and I mentioned can be found at https://www.moneypeach.com/session90

--- Support this podcast: https://anchor.fm/angularair/support

AiA 152: Multirepo vs Monorepo with Jeff Whelpley and Kushal Dave On today's episode of Adventures in Angular, we have panelists Ward Bell, Joe Eames and Charles Max Wood. We have special guests, Jeff Whelpley and Kushal Dave. The discussion ranges from the organization of code bases to the benefits of using Monorepo vs Multirepo. Tune in! [00:01:45] – Introduction to Jeff Whelpley and Kushal Dave Kushal is CTO at Scroll, a start-up. Before that, he was at Foursquare, Chartbeat, Google, and IBM. He has worked in a lot of monorepo code base. Although he actually has experience working on a lot of Multirepo situations. Jeff is the CTO of a small startup in Boston called GetHuman that helps people with customer service problems. He has been on Adventures in Angular a couple of times before. He has also been in a couple of other podcasts before, as well as in the open-source community. [00:03:20] – Introduction to the issue Typically, when you’re working in just one or two people team, you don’t really have that many issues centered on dev process, coordinating changes between each other, and trying to figure out the best optimal way to organize your code. Most of the time, you understand the entire code base because you’re working with everything. It gets to be a much different problem once you get to have a larger team. In essence, everything is starting slow down because of different overhead related to the process that was needed in order to make sure got quality changes. You basically have to spend a lot of time and thought around your developer process, how you structure your code, how you physically setup, and organize your entire code base. [00:06:20] – How to organize your code bases? When Kushal worked at Google, everything is in a single giant repository. There are one or two exceptions for client code and some infrastructure things. It allowed people to feel that they could change any of the code and it made it easy to keep everybody in sync with the state of the code. There is some sort of workflow and process things that you have to change in order to get that right. Probably, the biggest one is trying to keep the repo from working in long running branches because things start to diverge. That was the model of Foursquare too. [00:08:15] – How do you run all of the CI across everything? The answer changes to different sizes. At Scroll and for most of the time that Kushal was at Foursquare, it was efficient to run all the builds on every commit. If you just have one mega build that just runs continuously, that’s good enough up until 30 or 40 developers. Once you hit that size, there’s a variety of build tools out there that you can use and understand the structure of your code base. Once you’ve used one of these build tools, declaratively indicate which artifacts depends on which libraries, and what the full dependency thing is, you can build only the relevant CI’s. You can decide whether this change only touches this binary or this test. Chuck also like the approach of having everything in master. If it was experimental, it would still go into master and their CI would effectively run the different builds with the different feature flags. If what you did broke something that somebody else was working on in a process, you could just adjust it midstream. [00:16:00] – Gatekeeper process The gatekeeper process protects the whole code base but at the same time, it’s in the layer of bureaucracy. We’ve been reviewing every piece of code before it’s allowed to land in master. Everybody on our team commits multiple times a day to master. All the changes, as much as possible are really small, especially the feature flag check. In that world, there is this bureaucracy. Hopefully, it’s not holding you up too much. The flipside of that is when you’ll feel really confident that you didn’t break anybody who depends on you and you’re going to have to revisit this change a month from now. For the past 9 months or so, Jeff tried a bunch of different configurations. He tried monorepo and other configurations from the other end of the spectrum - many small packages. As he was interviewing people with their different setups, they’ve all encountered the same types of problems. Regardless if you’re using monorepo or not, as long as you’re trying to keep your changes small and specific, and implemented quickly, it can alleviate any other pains. [00:22:10] – Guard rails The guard rails are just the reviewers. For us, every change that’s getting reviewed means that in some extent, there’s a human check on that. I’m not sure if you can but I certainly know that Reviewable and Fabricate both offer sort of wide range of configuration options. I can imagine the world in which you can programmatically keep people from landing changes that didn’t have that level. In Github, there are guard rails. That actually helps the reviewers. It’s reassuring to have some technology that this person is associated with this set of boundaries. If you want to step outside of the boundaries, they’re going to have to get some other person who understands the code that’s outside of the line to join in approving that. If their organization is big, this is something that they might have to think about. Jeff advises to really be careful about what you’re doing. Is this a change where you are just bumping version numbers or is this something that you have to change a business logic? [00:28:15] – Allowing different people to upgrade dependencies The only way Kushal has ever seen it done is a brutal all-nighter by somebody who has to sit there and get everything working. But one of the things that Google does is they develop a lot of patterns about how to refactor code to make things easier. One solution that Jeff sees is the complete opposite of the spectrum from monorepo. Dr. Gleb Bahmutov is a huge fan of open-source smaller repos - a lot of the mentality of keeping things small, separate and distinct. He’s decided that he’s going to stick in the many repo universe and just create tooling to solve some of these problems. For versioning, he runs this server that detects that a new version has been published. It will automatically try to update it and run all the tests. But according to Kushal, if you have different repos, you can move differently in terms of dependencies but if you’re now out of sync, you may suddenly have incompatible dependencies across what you’re doing. It’s a question of when you want to deal with the problem. Chuck talks about the ways you can get out of sync. With the multirepo, you can get out of sync not just on the dependencies and the build process, but also on the API’s. If you have a module that you’re working on over here and whatever are consuming it on the other side as a driver may not be updated yet so it doesn’t talk properly. Jeff also noticed that with Angular DI, if you aren’t actually using the same version, you run into issues because it has to be the exact same thing at every level or else the injection token is different. [00:36:50] – Develop within Monorepo or develop in a separate repo Chuck thinks that it depends. If there are a lot of dependencies and shortcuts that he can take by relying on the monorepo, he will do it on the monorepo like if it auto loads the correct libraries automatically. And then, they don’t have to do a whole lot of setup. If it’s small, independent, and it’s going to move quickly, then, a separate repo may be the right answer. Kushal adds that there are a lot of benefits in doing it in the monorepo. With feature flags, you have the benefit of reviewing it. It also allows you and others to keep up with everyone in terms of breaking API changes, other than having some brutal merge. Jeff will do it in a separate repo. If this an experimental thing, it disturbs people less. It alleviates the notifications that go on. That is why Kushal’s team also built a lot of custom Slack cooks in order to get some notifications tailored to the parts that they only care about. [00:44:50] – How do you work it out so that things aren’t so tightly coupled? There are no circular dependencies between your packages even transitively. As your monorepo grows you may eventually have some tooling that requires that for your build system. Can this layer have this type of functionality? Or does it need to be moved into a new package? It also means it improves your architecture. Kushal’s team is working on Java. This object that users and organizations create can know about each other’s’ objects but the users can never depend back into organizations or vice versa. You can think of the layered model of networking. We have the pure data model objects are not allowed to know anything about the service layer that interacts with the database. The database can know about those model objects. The web tier can obviously know about both the model objects and the service tier because it utilizes both of those. [00:47:30] – How are those relationships defined? They are defined in build files. If you look at Pants or Blaze or Buck, all those build systems have explicit dependency configurations so you can sort of keeping any of those invariants from being broken.  But Kushal’s team just have a Wiki page that lists out the rules. They also have a test that looks for any cycles in any package dependencies. Jeff’s team created a CLI tool that walks down all subdirectories from where they’re running it. It finds all the package JSON in all your subdirectories and it creates the dependency graphs. They haven’t fully moved to a monorepo but they did start to consolidate. They have a couple of larger repos. This tool will see the dependency graph for all the NPM modules and also see the dependencies between the repos based off of the NPM module dependencies. [00:50:20] – Multimonorepo It’s not perfect to have one larger repo that has basically all of the none-deployable codes. Jeff and his team have a separate set of repos for the actual deployable code. They haven’t made the jump to where Kushal is advocating – using build tools. [00:50:20] – To open-source When you want an open-source portion of what you’re doing but not the entire company’s code base, Jeff thinks that there’s really no way out of having a separate repo for that. Google has this giant internal repo because not everything in it is open-source. Angular is open-source. That’s at least one driver that Angular is in the public Github repo and Google use so much of Angular. And some companies want the sort of open collaboration and free support and upgrades from the community. Other companies see that they’re giving away some kind of competitive advantage that they’re not willing to give up. [00:55:40] – Monorepo is better in all cases Jeff recognizes that there’s a number of organizations that have successfully implemented it but there isn’t an easy way for someone to do it. It’s not common knowledge and does not have a well-known set of tooling and best practices. There’s still a lot to go to get to the point where it’s a no-brainer and everybody knows how to do this the right way. Ward doesn’t know how to do a monorepo but according to him, if he is in an organization or starting an organization, he would go figure out how to do it and would want his organization to have a monorepo. Chuck tends to lean to monorepo but doesn't always do it either. Another caveat is even if he starts with the monorepo, that doesn’t mean that’s where he’s going to end. The answer is if you put them all in separate repos and it turns out that you need benefits of having them all in the same place, you can move them all in one repo. It may not be easy depending on how big and complicated you make your mono or the way you tie together your disparate repos. Kushal is all in. The only time that he wouldn’t do it is if he’s building disparate open-source projects and wanted them to play the open-source ecosystem. The net benefit is that everyone is moving together rapidly because monorepo is optimized for speed. But Kushal wishes that the tooling is better and that many people move to this model. Joe is also open to monorepo in a larger organization. He thinks that the separate repos keep things but monorepo can solve a lot of problems. [01:01:55] – Places to go Jeff has a bunch of articles for people who are pro-monorepo and are advocating for that. He has yet to find one that sets forth like a good mental model or decision framework. This is what Jeff hopes to create in the next couple of weeks before the conference. Picks Ward Bell Hiking Fishing Southern Sierras Chuck Max Wood Book: Profit First by Mike Michalowicz Ketogenic Diet Air-conditioning Joe Eames Book: Everybody Lies: Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are by Seth Stephens-Davidowitz Rent a scooter to ride around Rome Jeff Whelpley Survey: Monorepo vs Multirepo Twitter: @jeffwhelpley Medium: @jeffwhelpey Kushal Dave Technical Design Reviews Book: The Orphan Master’s Son Twitter: @krave Medium: Workflow

AiA 152: Multirepo vs Monorepo with Jeff Whelpley and Kushal Dave On today's episode of Adventures in Angular, we have panelists Ward Bell, Joe Eames and Charles Max Wood. We have special guests, Jeff Whelpley and Kushal Dave. The discussion ranges from the organization of code bases to the benefits of using Monorepo vs Multirepo. Tune in! [00:01:45] – Introduction to Jeff Whelpley and Kushal Dave Kushal is CTO at Scroll, a start-up. Before that, he was at Foursquare, Chartbeat, Google, and IBM. He has worked in a lot of monorepo code base. Although he actually has experience working on a lot of Multirepo situations. Jeff is the CTO of a small startup in Boston called GetHuman that helps people with customer service problems. He has been on Adventures in Angular a couple of times before. He has also been in a couple of other podcasts before, as well as in the open-source community. [00:03:20] – Introduction to the issue Typically, when you’re working in just one or two people team, you don’t really have that many issues centered on dev process, coordinating changes between each other, and trying to figure out the best optimal way to organize your code. Most of the time, you understand the entire code base because you’re working with everything. It gets to be a much different problem once you get to have a larger team. In essence, everything is starting slow down because of different overhead related to the process that was needed in order to make sure got quality changes. You basically have to spend a lot of time and thought around your developer process, how you structure your code, how you physically setup, and organize your entire code base. [00:06:20] – How to organize your code bases? When Kushal worked at Google, everything is in a single giant repository. There are one or two exceptions for client code and some infrastructure things. It allowed people to feel that they could change any of the code and it made it easy to keep everybody in sync with the state of the code. There is some sort of workflow and process things that you have to change in order to get that right. Probably, the biggest one is trying to keep the repo from working in long running branches because things start to diverge. That was the model of Foursquare too. [00:08:15] – How do you run all of the CI across everything? The answer changes to different sizes. At Scroll and for most of the time that Kushal was at Foursquare, it was efficient to run all the builds on every commit. If you just have one mega build that just runs continuously, that’s good enough up until 30 or 40 developers. Once you hit that size, there’s a variety of build tools out there that you can use and understand the structure of your code base. Once you’ve used one of these build tools, declaratively indicate which artifacts depends on which libraries, and what the full dependency thing is, you can build only the relevant CI’s. You can decide whether this change only touches this binary or this test. Chuck also like the approach of having everything in master. If it was experimental, it would still go into master and their CI would effectively run the different builds with the different feature flags. If what you did broke something that somebody else was working on in a process, you could just adjust it midstream. [00:16:00] – Gatekeeper process The gatekeeper process protects the whole code base but at the same time, it’s in the layer of bureaucracy. We’ve been reviewing every piece of code before it’s allowed to land in master. Everybody on our team commits multiple times a day to master. All the changes, as much as possible are really small, especially the feature flag check. In that world, there is this bureaucracy. Hopefully, it’s not holding you up too much. The flipside of that is when you’ll feel really confident that you didn’t break anybody who depends on you and you’re going to have to revisit this change a month from now. For the past 9 months or so, Jeff tried a bunch of different configurations. He tried monorepo and other configurations from the other end of the spectrum - many small packages. As he was interviewing people with their different setups, they’ve all encountered the same types of problems. Regardless if you’re using monorepo or not, as long as you’re trying to keep your changes small and specific, and implemented quickly, it can alleviate any other pains. [00:22:10] – Guard rails The guard rails are just the reviewers. For us, every change that’s getting reviewed means that in some extent, there’s a human check on that. I’m not sure if you can but I certainly know that Reviewable and Fabricate both offer sort of wide range of configuration options. I can imagine the world in which you can programmatically keep people from landing changes that didn’t have that level. In Github, there are guard rails. That actually helps the reviewers. It’s reassuring to have some technology that this person is associated with this set of boundaries. If you want to step outside of the boundaries, they’re going to have to get some other person who understands the code that’s outside of the line to join in approving that. If their organization is big, this is something that they might have to think about. Jeff advises to really be careful about what you’re doing. Is this a change where you are just bumping version numbers or is this something that you have to change a business logic? [00:28:15] – Allowing different people to upgrade dependencies The only way Kushal has ever seen it done is a brutal all-nighter by somebody who has to sit there and get everything working. But one of the things that Google does is they develop a lot of patterns about how to refactor code to make things easier. One solution that Jeff sees is the complete opposite of the spectrum from monorepo. Dr. Gleb Bahmutov is a huge fan of open-source smaller repos - a lot of the mentality of keeping things small, separate and distinct. He’s decided that he’s going to stick in the many repo universe and just create tooling to solve some of these problems. For versioning, he runs this server that detects that a new version has been published. It will automatically try to update it and run all the tests. But according to Kushal, if you have different repos, you can move differently in terms of dependencies but if you’re now out of sync, you may suddenly have incompatible dependencies across what you’re doing. It’s a question of when you want to deal with the problem. Chuck talks about the ways you can get out of sync. With the multirepo, you can get out of sync not just on the dependencies and the build process, but also on the API’s. If you have a module that you’re working on over here and whatever are consuming it on the other side as a driver may not be updated yet so it doesn’t talk properly. Jeff also noticed that with Angular DI, if you aren’t actually using the same version, you run into issues because it has to be the exact same thing at every level or else the injection token is different. [00:36:50] – Develop within Monorepo or develop in a separate repo Chuck thinks that it depends. If there are a lot of dependencies and shortcuts that he can take by relying on the monorepo, he will do it on the monorepo like if it auto loads the correct libraries automatically. And then, they don’t have to do a whole lot of setup. If it’s small, independent, and it’s going to move quickly, then, a separate repo may be the right answer. Kushal adds that there are a lot of benefits in doing it in the monorepo. With feature flags, you have the benefit of reviewing it. It also allows you and others to keep up with everyone in terms of breaking API changes, other than having some brutal merge. Jeff will do it in a separate repo. If this an experimental thing, it disturbs people less. It alleviates the notifications that go on. That is why Kushal’s team also built a lot of custom Slack cooks in order to get some notifications tailored to the parts that they only care about. [00:44:50] – How do you work it out so that things aren’t so tightly coupled? There are no circular dependencies between your packages even transitively. As your monorepo grows you may eventually have some tooling that requires that for your build system. Can this layer have this type of functionality? Or does it need to be moved into a new package? It also means it improves your architecture. Kushal’s team is working on Java. This object that users and organizations create can know about each other’s’ objects but the users can never depend back into organizations or vice versa. You can think of the layered model of networking. We have the pure data model objects are not allowed to know anything about the service layer that interacts with the database. The database can know about those model objects. The web tier can obviously know about both the model objects and the service tier because it utilizes both of those. [00:47:30] – How are those relationships defined? They are defined in build files. If you look at Pants or Blaze or Buck, all those build systems have explicit dependency configurations so you can sort of keeping any of those invariants from being broken.  But Kushal’s team just have a Wiki page that lists out the rules. They also have a test that looks for any cycles in any package dependencies. Jeff’s team created a CLI tool that walks down all subdirectories from where they’re running it. It finds all the package JSON in all your subdirectories and it creates the dependency graphs. They haven’t fully moved to a monorepo but they did start to consolidate. They have a couple of larger repos. This tool will see the dependency graph for all the NPM modules and also see the dependencies between the repos based off of the NPM module dependencies. [00:50:20] – Multimonorepo It’s not perfect to have one larger repo that has basically all of the none-deployable codes. Jeff and his team have a separate set of repos for the actual deployable code. They haven’t made the jump to where Kushal is advocating – using build tools. [00:50:20] – To open-source When you want an open-source portion of what you’re doing but not the entire company’s code base, Jeff thinks that there’s really no way out of having a separate repo for that. Google has this giant internal repo because not everything in it is open-source. Angular is open-source. That’s at least one driver that Angular is in the public Github repo and Google use so much of Angular. And some companies want the sort of open collaboration and free support and upgrades from the community. Other companies see that they’re giving away some kind of competitive advantage that they’re not willing to give up. [00:55:40] – Monorepo is better in all cases Jeff recognizes that there’s a number of organizations that have successfully implemented it but there isn’t an easy way for someone to do it. It’s not common knowledge and does not have a well-known set of tooling and best practices. There’s still a lot to go to get to the point where it’s a no-brainer and everybody knows how to do this the right way. Ward doesn’t know how to do a monorepo but according to him, if he is in an organization or starting an organization, he would go figure out how to do it and would want his organization to have a monorepo. Chuck tends to lean to monorepo but doesn't always do it either. Another caveat is even if he starts with the monorepo, that doesn’t mean that’s where he’s going to end. The answer is if you put them all in separate repos and it turns out that you need benefits of having them all in the same place, you can move them all in one repo. It may not be easy depending on how big and complicated you make your mono or the way you tie together your disparate repos. Kushal is all in. The only time that he wouldn’t do it is if he’s building disparate open-source projects and wanted them to play the open-source ecosystem. The net benefit is that everyone is moving together rapidly because monorepo is optimized for speed. But Kushal wishes that the tooling is better and that many people move to this model. Joe is also open to monorepo in a larger organization. He thinks that the separate repos keep things but monorepo can solve a lot of problems. [01:01:55] – Places to go Jeff has a bunch of articles for people who are pro-monorepo and are advocating for that. He has yet to find one that sets forth like a good mental model or decision framework. This is what Jeff hopes to create in the next couple of weeks before the conference. Picks Ward Bell Hiking Fishing Southern Sierras Chuck Max Wood Book: Profit First by Mike Michalowicz Ketogenic Diet Air-conditioning Joe Eames Book: Everybody Lies: Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are by Seth Stephens-Davidowitz Rent a scooter to ride around Rome Jeff Whelpley Survey: Monorepo vs Multirepo Twitter: @jeffwhelpley Medium: @jeffwhelpey Kushal Dave Technical Design Reviews Book: The Orphan Master’s Son Twitter: @krave Medium: Workflow

--- Support this podcast: https://anchor.fm/angularair/support

AiA 152: Multirepo vs Monorepo with Jeff Whelpley and Kushal Dave On today's episode of Adventures in Angular, we have panelists Ward Bell, Joe Eames and Charles Max Wood. We have special guests, Jeff Whelpley and Kushal Dave. The discussion ranges from the organization of code bases to the benefits of using Monorepo vs Multirepo. Tune in! [00:01:45] – Introduction to Jeff Whelpley and Kushal Dave Kushal is CTO at Scroll, a start-up. Before that, he was at Foursquare, Chartbeat, Google, and IBM. He has worked in a lot of monorepo code base. Although he actually has experience working on a lot of Multirepo situations. Jeff is the CTO of a small startup in Boston called GetHuman that helps people with customer service problems. He has been on Adventures in Angular a couple of times before. He has also been in a couple of other podcasts before, as well as in the open-source community. [00:03:20] – Introduction to the issue Typically, when you’re working in just one or two people team, you don’t really have that many issues centered on dev process, coordinating changes between each other, and trying to figure out the best optimal way to organize your code. Most of the time, you understand the entire code base because you’re working with everything. It gets to be a much different problem once you get to have a larger team. In essence, everything is starting slow down because of different overhead related to the process that was needed in order to make sure got quality changes. You basically have to spend a lot of time and thought around your developer process, how you structure your code, how you physically setup, and organize your entire code base. [00:06:20] – How to organize your code bases? When Kushal worked at Google, everything is in a single giant repository. There are one or two exceptions for client code and some infrastructure things. It allowed people to feel that they could change any of the code and it made it easy to keep everybody in sync with the state of the code. There is some sort of workflow and process things that you have to change in order to get that right. Probably, the biggest one is trying to keep the repo from working in long running branches because things start to diverge. That was the model of Foursquare too. [00:08:15] – How do you run all of the CI across everything? The answer changes to different sizes. At Scroll and for most of the time that Kushal was at Foursquare, it was efficient to run all the builds on every commit. If you just have one mega build that just runs continuously, that’s good enough up until 30 or 40 developers. Once you hit that size, there’s a variety of build tools out there that you can use and understand the structure of your code base. Once you’ve used one of these build tools, declaratively indicate which artifacts depends on which libraries, and what the full dependency thing is, you can build only the relevant CI’s. You can decide whether this change only touches this binary or this test. Chuck also like the approach of having everything in master. If it was experimental, it would still go into master and their CI would effectively run the different builds with the different feature flags. If what you did broke something that somebody else was working on in a process, you could just adjust it midstream. [00:16:00] – Gatekeeper process The gatekeeper process protects the whole code base but at the same time, it’s in the layer of bureaucracy. We’ve been reviewing every piece of code before it’s allowed to land in master. Everybody on our team commits multiple times a day to master. All the changes, as much as possible are really small, especially the feature flag check. In that world, there is this bureaucracy. Hopefully, it’s not holding you up too much. The flipside of that is when you’ll feel really confident that you didn’t break anybody who depends on you and you’re going to have to revisit this change a month from now. For the past 9 months or so, Jeff tried a bunch of different configurations. He tried monorepo and other configurations from the other end of the spectrum - many small packages. As he was interviewing people with their different setups, they’ve all encountered the same types of problems. Regardless if you’re using monorepo or not, as long as you’re trying to keep your changes small and specific, and implemented quickly, it can alleviate any other pains. [00:22:10] – Guard rails The guard rails are just the reviewers. For us, every change that’s getting reviewed means that in some extent, there’s a human check on that. I’m not sure if you can but I certainly know that Reviewable and Fabricate both offer sort of wide range of configuration options. I can imagine the world in which you can programmatically keep people from landing changes that didn’t have that level. In Github, there are guard rails. That actually helps the reviewers. It’s reassuring to have some technology that this person is associated with this set of boundaries. If you want to step outside of the boundaries, they’re going to have to get some other person who understands the code that’s outside of the line to join in approving that. If their organization is big, this is something that they might have to think about. Jeff advises to really be careful about what you’re doing. Is this a change where you are just bumping version numbers or is this something that you have to change a business logic? [00:28:15] – Allowing different people to upgrade dependencies The only way Kushal has ever seen it done is a brutal all-nighter by somebody who has to sit there and get everything working. But one of the things that Google does is they develop a lot of patterns about how to refactor code to make things easier. One solution that Jeff sees is the complete opposite of the spectrum from monorepo. Dr. Gleb Bahmutov is a huge fan of open-source smaller repos - a lot of the mentality of keeping things small, separate and distinct. He’s decided that he’s going to stick in the many repo universe and just create tooling to solve some of these problems. For versioning, he runs this server that detects that a new version has been published. It will automatically try to update it and run all the tests. But according to Kushal, if you have different repos, you can move differently in terms of dependencies but if you’re now out of sync, you may suddenly have incompatible dependencies across what you’re doing. It’s a question of when you want to deal with the problem. Chuck talks about the ways you can get out of sync. With the multirepo, you can get out of sync not just on the dependencies and the build process, but also on the API’s. If you have a module that you’re working on over here and whatever are consuming it on the other side as a driver may not be updated yet so it doesn’t talk properly. Jeff also noticed that with Angular DI, if you aren’t actually using the same version, you run into issues because it has to be the exact same thing at every level or else the injection token is different. [00:36:50] – Develop within Monorepo or develop in a separate repo Chuck thinks that it depends. If there are a lot of dependencies and shortcuts that he can take by relying on the monorepo, he will do it on the monorepo like if it auto loads the correct libraries automatically. And then, they don’t have to do a whole lot of setup. If it’s small, independent, and it’s going to move quickly, then, a separate repo may be the right answer. Kushal adds that there are a lot of benefits in doing it in the monorepo. With feature flags, you have the benefit of reviewing it. It also allows you and others to keep up with everyone in terms of breaking API changes, other than having some brutal merge. Jeff will do it in a separate repo. If this an experimental thing, it disturbs people less. It alleviates the notifications that go on. That is why Kushal’s team also built a lot of custom Slack cooks in order to get some notifications tailored to the parts that they only care about. [00:44:50] – How do you work it out so that things aren’t so tightly coupled? There are no circular dependencies between your packages even transitively. As your monorepo grows you may eventually have some tooling that requires that for your build system. Can this layer have this type of functionality? Or does it need to be moved into a new package? It also means it improves your architecture. Kushal’s team is working on Java. This object that users and organizations create can know about each other’s’ objects but the users can never depend back into organizations or vice versa. You can think of the layered model of networking. We have the pure data model objects are not allowed to know anything about the service layer that interacts with the database. The database can know about those model objects. The web tier can obviously know about both the model objects and the service tier because it utilizes both of those. [00:47:30] – How are those relationships defined? They are defined in build files. If you look at Pants or Blaze or Buck, all those build systems have explicit dependency configurations so you can sort of keeping any of those invariants from being broken.  But Kushal’s team just have a Wiki page that lists out the rules. They also have a test that looks for any cycles in any package dependencies. Jeff’s team created a CLI tool that walks down all subdirectories from where they’re running it. It finds all the package JSON in all your subdirectories and it creates the dependency graphs. They haven’t fully moved to a monorepo but they did start to consolidate. They have a couple of larger repos. This tool will see the dependency graph for all the NPM modules and also see the dependencies between the repos based off of the NPM module dependencies. [00:50:20] – Multimonorepo It’s not perfect to have one larger repo that has basically all of the none-deployable codes. Jeff and his team have a separate set of repos for the actual deployable code. They haven’t made the jump to where Kushal is advocating – using build tools. [00:50:20] – To open-source When you want an open-source portion of what you’re doing but not the entire company’s code base, Jeff thinks that there’s really no way out of having a separate repo for that. Google has this giant internal repo because not everything in it is open-source. Angular is open-source. That’s at least one driver that Angular is in the public Github repo and Google use so much of Angular. And some companies want the sort of open collaboration and free support and upgrades from the community. Other companies see that they’re giving away some kind of competitive advantage that they’re not willing to give up. [00:55:40] – Monorepo is better in all cases Jeff recognizes that there’s a number of organizations that have successfully implemented it but there isn’t an easy way for someone to do it. It’s not common knowledge and does not have a well-known set of tooling and best practices. There’s still a lot to go to get to the point where it’s a no-brainer and everybody knows how to do this the right way. Ward doesn’t know how to do a monorepo but according to him, if he is in an organization or starting an organization, he would go figure out how to do it and would want his organization to have a monorepo. Chuck tends to lean to monorepo but doesn't always do it either. Another caveat is even if he starts with the monorepo, that doesn’t mean that’s where he’s going to end. The answer is if you put them all in separate repos and it turns out that you need benefits of having them all in the same place, you can move them all in one repo. It may not be easy depending on how big and complicated you make your mono or the way you tie together your disparate repos. Kushal is all in. The only time that he wouldn’t do it is if he’s building disparate open-source projects and wanted them to play the open-source ecosystem. The net benefit is that everyone is moving together rapidly because monorepo is optimized for speed. But Kushal wishes that the tooling is better and that many people move to this model. Joe is also open to monorepo in a larger organization. He thinks that the separate repos keep things but monorepo can solve a lot of problems. [01:01:55] – Places to go Jeff has a bunch of articles for people who are pro-monorepo and are advocating for that. He has yet to find one that sets forth like a good mental model or decision framework. This is what Jeff hopes to create in the next couple of weeks before the conference. Picks Ward Bell Hiking Fishing Southern Sierras Chuck Max Wood Book: Profit First by Mike Michalowicz Ketogenic Diet Air-conditioning Joe Eames Book: Everybody Lies: Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are by Seth Stephens-Davidowitz Rent a scooter to ride around Rome Jeff Whelpley Survey: Monorepo vs Multirepo Twitter: @jeffwhelpley Medium: @jeffwhelpey Kushal Dave Technical Design Reviews Book: The Orphan Master’s Son Twitter: @krave Medium: Workflow

Episode notes and links can be found at: https://angularair.com/#episode-102 --- Support this podcast: https://anchor.fm/angularair/support

Jeff is a Google Developer Expert, Boston AI Meet-up co-organizer, and a Boston Angular Meet-up co-organizer. He has been a guest in Adventures in Angular for a couple of times already. He also  spoke  at the Angular Remote Conference last year. Tune in to My Angular Story Jeff Whelpley to know more about what he is now up to and his story on programming.

Jeff is a Google Developer Expert, Boston AI Meet-up co-organizer, and a Boston Angular Meet-up co-organizer. He has been a guest in Adventures in Angular for a couple of times already. He also  spoke  at the Angular Remote Conference last year. Tune in to My Angular Story Jeff Whelpley to know more about what he is now up to and his story on programming.

Jeff is a Google Developer Expert, Boston AI Meet-up co-organizer, and a Boston Angular Meet-up co-organizer. He has been a guest in Adventures in Angular for a couple of times already. He also  spoke  at the Angular Remote Conference last year. Tune in to My Angular Story Jeff Whelpley to know more about what he is now up to and his story on programming.

On today’s episode, Charles Max Wood, Joe Eames, John Papa, Ward Bell, Alyssa Nicoll, Jeff Whelpley, and Dave Geddes discuss NG-Conf Speaker Selection Process. Tune in and learn how the organizers choose the speakers for the event!

On today’s episode, Charles Max Wood, Joe Eames, John Papa, Ward Bell, Alyssa Nicoll, Jeff Whelpley, and Dave Geddes discuss NG-Conf Speaker Selection Process. Tune in and learn how the organizers choose the speakers for the event!

On today’s episode, Charles Max Wood, Joe Eames, John Papa, Ward Bell, Alyssa Nicoll, Jeff Whelpley, and Dave Geddes discuss NG-Conf Speaker Selection Process. Tune in and learn how the organizers choose the speakers for the event!

Our 100th episode! Kent C. Dodds, Todd Motto and Jeff Whelpley join host Justin Schwartzenberger to talk about the history of the show. Episode notes and links can be found at: https://angularair.com/#episode-100 --- Support this podcast: https://anchor.fm/angularair/support

1:50 - Introducing Jeff Whelpley at Angular Remote Conf Twitter Github Angular Air 3:40 -  Working on Angular Air 6:25 - Lessons from Ben Lesh Episode Link 8:20 - Lessons from Gleb Bahmutov Episode Link 11:50 - Lessons from Aaron Frost Episode Link 14:00 - Lessons from Shai Reznik Episode Link 16:50 - Lessons from Joe Eames Episode Link 19:10 - Lessons from Uri Goldshtein 21:40 - Lessons from Wesley Cho and Jesus Rodriguez Episode Link 25:40 - Lessons from Brad Green 28:50 - Lessons from Igor Minar 31:40 - Lessons from Victor Savkin and Dan Abramov Episode Link 34:30 - Lessons from Amy Knight 36:05 - Lessons from Patrick Stapleton 39:00 - Lessons from Jamie King and Kyle Newman Fanboys movie Episode Link

1:50 - Introducing Jeff Whelpley at Angular Remote Conf Twitter Github Angular Air 3:40 -  Working on Angular Air 6:25 - Lessons from Ben Lesh Episode Link 8:20 - Lessons from Gleb Bahmutov Episode Link 11:50 - Lessons from Aaron Frost Episode Link 14:00 - Lessons from Shai Reznik Episode Link 16:50 - Lessons from Joe Eames Episode Link 19:10 - Lessons from Uri Goldshtein 21:40 - Lessons from Wesley Cho and Jesus Rodriguez Episode Link 25:40 - Lessons from Brad Green 28:50 - Lessons from Igor Minar 31:40 - Lessons from Victor Savkin and Dan Abramov Episode Link 34:30 - Lessons from Amy Knight 36:05 - Lessons from Patrick Stapleton 39:00 - Lessons from Jamie King and Kyle Newman Fanboys movie Episode Link

1:50 - Introducing Jeff Whelpley at Angular Remote Conf Twitter Github Angular Air 3:40 -  Working on Angular Air 6:25 - Lessons from Ben Lesh Episode Link 8:20 - Lessons from Gleb Bahmutov Episode Link 11:50 - Lessons from Aaron Frost Episode Link 14:00 - Lessons from Shai Reznik Episode Link 16:50 - Lessons from Joe Eames Episode Link 19:10 - Lessons from Uri Goldshtein 21:40 - Lessons from Wesley Cho and Jesus Rodriguez Episode Link 25:40 - Lessons from Brad Green 28:50 - Lessons from Igor Minar 31:40 - Lessons from Victor Savkin and Dan Abramov Episode Link 34:30 - Lessons from Amy Knight 36:05 - Lessons from Patrick Stapleton 39:00 - Lessons from Jamie King and Kyle Newman Fanboys movie Episode Link

Today I’m honored to have Jeff Whelpley on the show. Jeff is the CTO at GetHuman, and a regular contributor to the Angular Open Source community through his video podcast AngularAir and the Angular Universal project. In this episode Jeff guides us on how we can all contribute to the open source community

02:05 - Jeff Whelpley Introduction and Angular Universal Patterns Twitter Blog Jeffrey Whelpey & Patrick Stapleton: Angular 2 Universal Patterns @ ng-conf angular/universal 03:26 - Backend Implementations 05:07 - Drawbacks zone.js 12:46 - Contribution Patrick Stapleton Tobias Bosch Jeff Cross 16:42 - Caching 19:04 - Other Gotchas Session State App Container 25:40 - The User Experience Hydration 31:29 - Installation and Running Angular Universal 33:24 - The Release Schedule   Picks BB-8 Sphero (Joe) Black Man in a White Coat: A Doctor's Reflections on Race and Medicine by Damon Tweedy (Joe) iPhreaks Show Episode 153: Using Mobile Devices to Manage Diabetes with Scott Hanselman (Chuck) The Freelancers' Show Episode 202: Live from MicroConf: Managing a Team with Anders Thue Pedersen (Chuck) DevChat.tv Survey (Chuck) GetHuman (Jeff)

02:05 - Jeff Whelpley Introduction and Angular Universal Patterns Twitter Blog Jeffrey Whelpey & Patrick Stapleton: Angular 2 Universal Patterns @ ng-conf angular/universal 03:26 - Backend Implementations 05:07 - Drawbacks zone.js 12:46 - Contribution Patrick Stapleton Tobias Bosch Jeff Cross 16:42 - Caching 19:04 - Other Gotchas Session State App Container 25:40 - The User Experience Hydration 31:29 - Installation and Running Angular Universal 33:24 - The Release Schedule   Picks BB-8 Sphero (Joe) Black Man in a White Coat: A Doctor's Reflections on Race and Medicine by Damon Tweedy (Joe) iPhreaks Show Episode 153: Using Mobile Devices to Manage Diabetes with Scott Hanselman (Chuck) The Freelancers' Show Episode 202: Live from MicroConf: Managing a Team with Anders Thue Pedersen (Chuck) DevChat.tv Survey (Chuck) GetHuman (Jeff)

02:05 - Jeff Whelpley Introduction and Angular Universal Patterns Twitter Blog Jeffrey Whelpey & Patrick Stapleton: Angular 2 Universal Patterns @ ng-conf angular/universal 03:26 - Backend Implementations 05:07 - Drawbacks zone.js 12:46 - Contribution Patrick Stapleton Tobias Bosch Jeff Cross 16:42 - Caching 19:04 - Other Gotchas Session State App Container 25:40 - The User Experience Hydration 31:29 - Installation and Running Angular Universal 33:24 - The Release Schedule   Picks BB-8 Sphero (Joe) Black Man in a White Coat: A Doctor's Reflections on Race and Medicine by Damon Tweedy (Joe) iPhreaks Show Episode 153: Using Mobile Devices to Manage Diabetes with Scott Hanselman (Chuck) The Freelancers' Show Episode 202: Live from MicroConf: Managing a Team with Anders Thue Pedersen (Chuck) DevChat.tv Survey (Chuck) GetHuman (Jeff)

53 ngAir - Angular 2 Reactive Redux with Victor Savkin and Dan Abramov    What is state? Is there a difference between UI state and persisted state?   What problems do people run into with state? Why is it hard to manage state? How to keep the state on the client in sync with the state on the server?   What are the popular patterns for managing state? What is used in Angular 1? Difference between the core ideas and implementations What does unidirectional mean?   What is Redux? Benefits of redux and similar patterns Is redux for sync state updates only and is making an HTTP request considered a non-pure inside   a reducer function? What is ngrx? How is the reactive version of redux different than traditional Redux?  What are your feelings on setting change detection strategy to OnPush? How would one go about debugging the state changes in Angular2?   Other general questions Thoughts on cycle.js? There is a pattern in Redux if you have the same object in multiple places, you use _id in everything but one.  How would this work with ngrx or another reactive approach? (custom pipe and helpers?) Rob/Victor: I was starting to think about an Angular 2 decorator that does something similar to the React Redux connect() function but then Rob said it was a bad idea because it will mess with precompilation. What is the deal?   Predictions for the future What approach will Angular 2 developers adopt? Will a reactive version of redux gain any traction in the React world?   Tips & Picks   Jeff Whelpley Links:  Tips:  Picks: Our new sponsor, [Auth0](https://auth0.com/)   Victor Savkin  Links: [Managing State in Angular 2 Apps.] ( http://victorsavkin.com/post/137821436516/managing-state-in-     angular-2-applications)   Tips: AceJump a great plugin for WebStorm.   Picks: Kurt Vonnegut "Mother Night", Brad Mehldau "10 Years Solo Live", Woody Allen "Manhattan Murder Mystery"   Gleb Bahmutov Links: [Rob Warmald’s talks] (http://www.roblog.io/angular2/talks/2015/11/29/angular2-data-talks.html) - Angular 2 data flow with nice examples   Tips: Everything in your application could be a source of events: button clicks, mouse movements, messages from the server, timer, etc.   Dan Abramov  Tips: No boilerplates   Picks: [Redux Saga](https://github.com/yelouafi/redux-saga) [aphrodite](https://github.com/Khan/aphrodite)   Patrick Stapleton Picks: [What’s new in Webpack 2] (https://gist.github.com/sokra/27b24881210b56bbaff7)   Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well.   AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

51 ngAir - Getting Past the Angular Learning Curve with Pascal Precht   What’s the story behind Thoughtram? What’s in a name? Overall Philosophy Why did you decide to teach? What is your approach to teaching? How do people learn? How many workshops do you give per month? Does it get tedious to teach the same thing to people over & over? Angular 1 Are you still doing Angular 1 training? What was hardest thing for people to grok with Angular 1? Angular 2 Do you see mostly people coming from Angular 1 or people totally new to Angular? What is the hardest thing for people to grok with Angular 2? How do you teach *ngFor in a way that makes sense for developers? Harder/easier to teach/learn than Angular 1? How do you manage staying involved in so many different projects? How is it to be a digital nomad? How long did it take until you could leave your daily jobs & work on Thoughtram full time? What do you think about Merrick Christiansen’s comments about not needing DI anymore since he has gone full functional programming?    Tips & Picks   Olivier Combe   Links: Read the source on Angular 2 Web Workers:  https://www.youtube.com/watch?v=5T2YySJISQw                      Picks: NG-Conf CFP, Angular Connect 2016   Jeff Whelpley      Picks: [Univesal Prerender](https://github.com/angular/universal-starter/tree/prerender) [20 Minute VC with Jeff Seibert] (http://www.thetwentyminutevc.com/jeffseibert/)   Pascal Picks: [Belgium Angular  Conference] (https://twitter.com/ngbeconf/status/690625713481846784 [Thoughtram Master Class](http://thoughtram.io/angular-master-class.html)            Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

TypeScript Deep Dive with Alex Eagle and Blake Embrey Sure, you can write Angular 2 in ES6 with Babel or even ES5, but most developers that try out TypeScript with Angular 2 never look back. Alex Eagle is on the Angular core team at Google and has been doing a lot of work to make sure Angular 2 works well with TypeScript. Blake Embrey is the creator of ts-node and a huge TypeScript enthusiast. Even if you have concerns about typing in JavaScript, listen to this episode to get the low down on why TypeScript rocks and how it is going to help you to build awesome apps in Angular 2.    Picks •                Alex Eagle http://www.typescriptlang.org/Playground https://basarat.gitbooks.io/typescript/content/ [TrumpScript] (https://github.com/samshadwell/TrumpScript) [Broccoli] (http://broccolijs.com) [ts-node] (https://github.com/TypeStrong/ts-node) •                Olivier Combe Links: Managing state in Angular 2 applications by Victor Savking: http://victorsavkin.com/post/137821436516/managing-state-in-angular-2-applications Tips:PhantomJS 2.1 has been released (1 year after 2.0), it’s time to upgrade •                Jeff Whelpley Tips:Try TypeScript  Picks: ▪                                                    Angular Air episode 50! ▪                                                    [Learn Angular Universal on Read the Source] ▪                                                    (http://hangouts.readthesource.io/hangouts/angular-universal/) [Nathan Walker and Angular CLI changes for 3rd party libs] (https://github.com/angular/angular-cli/pull/135) [Front end dev resources] (https://github.com/dmytroyarmak/frontend-dev-resources) Patrick Stapleton Tips:Provide feedback on problems you ran into for open-source projects. Picks: [Typings with Blake Embrey] (https://plus.google.com/events/c6sv2k75vi9q8fj0g0gkuqbt69o) [Learn TypeScript free workshop by Blake Embrey] (https://github.com/TypeStrong/learn-typescript) •                Ari Lerner Tips: Picks: [The Barisieur] (http://www.joshrenoufdesign.com/new-gallery-5/av7fqhie9y5ptdbxr9s4i8rb65irqo) [Activitaté] (http://www.withings.com/us/en/products/activite [Withings Aura] (https://www.withings.com/us/en/store/details/70035401) [Modern Romance] (http://www.amazon.com/Modern-Romance-Aziz-Ansari/dp/1594206279) Blake Embrey Tips:If you have issues, create issues, but remember to keep things actionableLearn TypeScript (or another typed language) and think about where else you could be applying type system semantics Picks: Reading everyday, before bed Currently reading: https://www.goodreads.com/book/show/6065215-the-strain   Forgot to mention on the show, but meetup! http://www.meetup.com/hello-world-sf/Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

What's new in RxJS 5.0? with Ben Lesh - RxJS is red hot right now in the JavaScript community and it is only going to get hotter once Angular 2 lands. Ben Lesh is a Senior UI Engineer at Netflix and is one of the core contributors to RxJS and has been focusing on the latest release (currently in beta) which is largely a rewrite. If you are unfamiliar with RxJS, join us to hear about the basics of Reactive Programming. If you have already started to us RxJS, join us to learn about all the cool changes coming with 5.0. This is one episode you are not going to want to miss! Panelists: Aimee Knight, Olivier Combe and PatrictJS Picks/Tips: Olivier - Everything is a Stream, Front end newsletter, A developer's guide to interviewing Aimee - Introduction to Reactive Programming - Egghead.io Jeff - Angular Universal Patrick - Read the Source: Angular Universal Ben - TC39 considered Observable spec, RxJS 5 repo, RxJS 5 docs, Netflix jobs and culture deck Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

Why empathy will make you a better developer with Joe Eames - One of the most amazing members of the Angular community joins us to talk about understanding your teammates and creating an awesome work environment. Panelists: Aimee Knight and PatrictJS Picks/Tips: Aimee - Introduction To Transpiler Jeff - Angular 2 and Redux Patrick - RxJS 5.0, FalcorJS Joe - Brene Brown Ted Talk, How to talk so kids will listen, Littlebits Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

How to become an open source contributor - Welsey Cho and Jesus Rodriguez from the ng-bootstrap team join us to talk about how and why you should get into open source development. Panelists: Olivier Combe, Aimee Knight and PatrictJS Picks/Tips: Jesus - FOSS Tips, Thoughtram Blog, [Merging vs Rebasing]( https://www.atlassian.com/git/tutorials/merging-vs-rebasing/) Olivier - Sebastian MacKenzie Year in Review, Webpack Angular 2 Starter, There will be blood, Jeff's response Aimee - Frontend Masters Advanced Javascript, JS Remote Conf Patrick - Docker Jeff - Pete Bacon Darwin AngularU talk on OSS Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

The panel talks about what will happen to Angular and JavaScript in general in 2016. Panelists: Aimee Knight, Olivier Combe and PatrictJS Picks/Tips: Aimee - JavaScript Developer Survey Results Jeff - Angular 2 Survey Results, Jeff's 2015 predictions Patrick - ng-nl Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

Star Wars - Kyle Newman, director of the Star War-related cult classic movie Fanboys joins the Angular Air crew and special guest Randall Koutnik to talk about Star Wars. No spoilers for episode 7! Also, stay tuned to the end to see a special apperance from Kyle's wife, the actress Jaime King. Panelists: PatrictJS Picks/Tips: Olivier - Star Wars Medley, Star Wars Review Kyle - Fanboys, The Franchise Podcast Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

43.5 ngAir - Angular 2 Beta - The Angular Team stops by to announce the arrival of Angular 2 Beta!!! Also, Thomas Burleson announces the 1.0 release of Angular Material. This show is amazing! Guests: Brad Green, Misko Hevery, Igor Minar, and Thomas Burleson Panelists: Olivier Combe, Aimee Knight, Scott Moss, Carmen Popoviciu, PatrictJS, and Jeff Whelpley Picks/Tips: Brad - Developer News Worldwide Misko - xkcd Igor - http2 Olivier - Auth0 Angular 2 Blog Posts Aimee - Read the Source Carmen - Light Table, Patrick - Angular 2 Beta Jeff - Aerobatic.com, RxJS 5.0 Beta Angular Air is a video podcast all about Angular hosted by Jeff Whelpley. Please visit the Angular Air website (http://angularair.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. AngularAir is sponsored by: AngularClass Learn AngularJS, Angular 2, and Modern Web Development form the best. Looking for corporate Angular training, want to host us, or Angular consulting? twitter: @AngularClass email: info@angularclass.com chat: Join AngularClass Chat --- Support this podcast: https://anchor.fm/angularair/support

02:28 - Ward Bell (and Co.’s) Documentation Contributions for Angular 2 05:39 - Peter Bacon Darwin (and Co.) & Jade 07:38 - John Papa and the Tour of Heroes Tutorial 09:01 - Geoff Goodman & Plunker 10:07 - GDE (Google Developer Expert) Program/Summit 13:37 - Thomas Burleson & Angular Material 16:07 - The Angular Team

02:28 - Ward Bell (and Co.’s) Documentation Contributions for Angular 2 05:39 - Peter Bacon Darwin (and Co.) & Jade 07:38 - John Papa and the Tour of Heroes Tutorial 09:01 - Geoff Goodman & Plunker 10:07 - GDE (Google Developer Expert) Program/Summit 13:37 - Thomas Burleson & Angular Material 16:07 - The Angular Team

02:28 - Ward Bell (and Co.’s) Documentation Contributions for Angular 2 05:39 - Peter Bacon Darwin (and Co.) & Jade 07:38 - John Papa and the Tour of Heroes Tutorial 09:01 - Geoff Goodman & Plunker 10:07 - GDE (Google Developer Expert) Program/Summit 13:37 - Thomas Burleson & Angular Material 16:07 - The Angular Team

Surprise Episode! - Olivier Combe has a surprise for everyone (including Kent C. Dodds) Guests: Vojta Jína, Jeff Cross, Shai Reznik, and Todd Motto Panelists: Olivier Combe, Aimee Knight, Carmen Popoviciu, Jeff Whelpley, and Rob Wormald Links: Open Source Stamina Angular Air is a video podcast all about Angular hosted by egghead.io instructor Kent C. Dodds. Please visit the Angular Air website (http://angular-air.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. --- Support this podcast: https://anchor.fm/angularair/support

AngularConnect Track 1 Playlist Track 2 Playlist   02:30 - Going to Beta AngularConnect Keynote with Brad Green, Igor Minar and Jules Kremer 09:23 - Angular 1.x Angular 1.5 and beyond with Pete Bacon Darwin and Lucas Mirelmann 17:39 - Peter’s Thoughts as an Organizer of AngularConnect 26:33 - Highlights Routing in Eleven Dimensions with Component Router with Brian Ford Full Stack Angular 2 with Jeff Whelpley and Patrick Stapleton ngAnimate 2 0 with Matias Niemelä Testing Strategies with Angular 2 with Julie Ralph Ionic 2 Getting started in Angular 2 with Rado Kirov and Naomi Black Building apps with Firebase and Angular 2 with Sara Robinson 31:46 - Soft Skills Talks Becoming Betazoid How to Listen and Empathize with Others in the Workplace with Joe Eames Optimize Yourself 5 Key Traits of High Performing Humans with Sylvana Rochet Getting Comfortable Being Uncomfortable with Aimee Knight (Super)Power Management with Igor Minar @ ng-conf 2015 35:03 - What is the next big Angular Conference on the horizon? ng-conf 2016 36:09 - Going to Beta (Cont’d) Better Concepts, Less Code in Angular 2 with Victor Savin and Tobias Bosch   44:19 - NativeScript Building native mobile apps with Angular 2 0 and NativeScript​ with Sebastian Witalec 47:06 - Angular Cheat Sheet Tutorial: Tour of Heros - Angular 2 for TypeScript 49:54 - Material Design   Joe’s List for ““talks to watch if you want to get up to date with Angular 2” AngularConnect Keynote with Brad Green, Igor Minar and Jules Kremer Angular 1.5 and beyond with Pete Bacon Darwin and Lucas Mirelmann Routing in Eleven Dimensions with Component Router with Brian Ford Getting started in Angular 2 with Rado Kirov and Naomi Black Angular 2 Data Flow with Jeff Cross and Alex Rickabaugh Better Concepts, Less Code in Angular 2 with Victor Savin and Tobias Bosch Google Angular Team Panel   Joe’s Additional Recommendations Using Web Workers for More Responsive Apps with Jason Teplitz Building native mobile apps with Angular 2 0 and NativeScript​ with Sebastian Witalec Reactive Streams in Angular 1 and 2 Ben Lesh   Suggest topics and guests! Contribute to the repo aiatopics!   Picks AngularConnect (Joe) Denmark (Joe) Star Wars: The Force Awakens Trailer (Official) (John) Ultimate t-shirt for trolling science fiction fans (Chuck) Rush Revere and the Brave Pilgrims by Rush Limbaugh (Chuck) The Magician's Nephew by C. S. Lewis (Chuck) MONEY Master the Game: 7 Simple Steps to Financial Freedom by Tony Robbins (Chuck)

AngularConnect Track 1 Playlist Track 2 Playlist   02:30 - Going to Beta AngularConnect Keynote with Brad Green, Igor Minar and Jules Kremer 09:23 - Angular 1.x Angular 1.5 and beyond with Pete Bacon Darwin and Lucas Mirelmann 17:39 - Peter’s Thoughts as an Organizer of AngularConnect 26:33 - Highlights Routing in Eleven Dimensions with Component Router with Brian Ford Full Stack Angular 2 with Jeff Whelpley and Patrick Stapleton ngAnimate 2 0 with Matias Niemelä Testing Strategies with Angular 2 with Julie Ralph Ionic 2 Getting started in Angular 2 with Rado Kirov and Naomi Black Building apps with Firebase and Angular 2 with Sara Robinson 31:46 - Soft Skills Talks Becoming Betazoid How to Listen and Empathize with Others in the Workplace with Joe Eames Optimize Yourself 5 Key Traits of High Performing Humans with Sylvana Rochet Getting Comfortable Being Uncomfortable with Aimee Knight (Super)Power Management with Igor Minar @ ng-conf 2015 35:03 - What is the next big Angular Conference on the horizon? ng-conf 2016 36:09 - Going to Beta (Cont’d) Better Concepts, Less Code in Angular 2 with Victor Savin and Tobias Bosch   44:19 - NativeScript Building native mobile apps with Angular 2 0 and NativeScript​ with Sebastian Witalec 47:06 - Angular Cheat Sheet Tutorial: Tour of Heros - Angular 2 for TypeScript 49:54 - Material Design   Joe’s List for ““talks to watch if you want to get up to date with Angular 2” AngularConnect Keynote with Brad Green, Igor Minar and Jules Kremer Angular 1.5 and beyond with Pete Bacon Darwin and Lucas Mirelmann Routing in Eleven Dimensions with Component Router with Brian Ford Getting started in Angular 2 with Rado Kirov and Naomi Black Angular 2 Data Flow with Jeff Cross and Alex Rickabaugh Better Concepts, Less Code in Angular 2 with Victor Savin and Tobias Bosch Google Angular Team Panel   Joe’s Additional Recommendations Using Web Workers for More Responsive Apps with Jason Teplitz Building native mobile apps with Angular 2 0 and NativeScript​ with Sebastian Witalec Reactive Streams in Angular 1 and 2 Ben Lesh   Suggest topics and guests! Contribute to the repo aiatopics!   Picks AngularConnect (Joe) Denmark (Joe) Star Wars: The Force Awakens Trailer (Official) (John) Ultimate t-shirt for trolling science fiction fans (Chuck) Rush Revere and the Brave Pilgrims by Rush Limbaugh (Chuck) The Magician's Nephew by C. S. Lewis (Chuck) MONEY Master the Game: 7 Simple Steps to Financial Freedom by Tony Robbins (Chuck)

AngularConnect Track 1 Playlist Track 2 Playlist   02:30 - Going to Beta AngularConnect Keynote with Brad Green, Igor Minar and Jules Kremer 09:23 - Angular 1.x Angular 1.5 and beyond with Pete Bacon Darwin and Lucas Mirelmann 17:39 - Peter’s Thoughts as an Organizer of AngularConnect 26:33 - Highlights Routing in Eleven Dimensions with Component Router with Brian Ford Full Stack Angular 2 with Jeff Whelpley and Patrick Stapleton ngAnimate 2 0 with Matias Niemelä Testing Strategies with Angular 2 with Julie Ralph Ionic 2 Getting started in Angular 2 with Rado Kirov and Naomi Black Building apps with Firebase and Angular 2 with Sara Robinson 31:46 - Soft Skills Talks Becoming Betazoid How to Listen and Empathize with Others in the Workplace with Joe Eames Optimize Yourself 5 Key Traits of High Performing Humans with Sylvana Rochet Getting Comfortable Being Uncomfortable with Aimee Knight (Super)Power Management with Igor Minar @ ng-conf 2015 35:03 - What is the next big Angular Conference on the horizon? ng-conf 2016 36:09 - Going to Beta (Cont’d) Better Concepts, Less Code in Angular 2 with Victor Savin and Tobias Bosch   44:19 - NativeScript Building native mobile apps with Angular 2 0 and NativeScript​ with Sebastian Witalec 47:06 - Angular Cheat Sheet Tutorial: Tour of Heros - Angular 2 for TypeScript 49:54 - Material Design   Joe’s List for ““talks to watch if you want to get up to date with Angular 2” AngularConnect Keynote with Brad Green, Igor Minar and Jules Kremer Angular 1.5 and beyond with Pete Bacon Darwin and Lucas Mirelmann Routing in Eleven Dimensions with Component Router with Brian Ford Getting started in Angular 2 with Rado Kirov and Naomi Black Angular 2 Data Flow with Jeff Cross and Alex Rickabaugh Better Concepts, Less Code in Angular 2 with Victor Savin and Tobias Bosch Google Angular Team Panel   Joe’s Additional Recommendations Using Web Workers for More Responsive Apps with Jason Teplitz Building native mobile apps with Angular 2 0 and NativeScript​ with Sebastian Witalec Reactive Streams in Angular 1 and 2 Ben Lesh   Suggest topics and guests! Contribute to the repo aiatopics!   Picks AngularConnect (Joe) Denmark (Joe) Star Wars: The Force Awakens Trailer (Official) (John) Ultimate t-shirt for trolling science fiction fans (Chuck) Rush Revere and the Brave Pilgrims by Rush Limbaugh (Chuck) The Magician's Nephew by C. S. Lewis (Chuck) MONEY Master the Game: 7 Simple Steps to Financial Freedom by Tony Robbins (Chuck)

Sign up for Angular Remote Conf!   02:35 - Jeff Whelpley Introduction Twitter Blog GetHuman Angular Air 02:53 - Patrick Stapleton Introduction Twitter GitHhub Blog Angular Class 03:39 - Advantages of Server Rendering 14:28 - Universal & Isomorphic 24:11 - Caching and Load Balancing Rendering the Application Rendering the Application with Data 41:29 - Service Worker 43:02 - Bindings 46:36 - Rendering Angular 49:00 - Prerendering 52:41 - Rendering in Angular 2 58:38 - Time Table Picks 14 by Peter Clines (Lukas) ZPacks Cuben Fiber Arc Backpacks (Ward) Angular Remote Conf (Chuck) Iron Sharpens Iron (Chuck) View from the Top (Chuck) GetHuman (Jeff) Angular Universal (Jeff) Open Source (Patrick) Angular Summit (Patrick) AngularConnect (Patrick)

Sign up for Angular Remote Conf!   02:35 - Jeff Whelpley Introduction Twitter Blog GetHuman Angular Air 02:53 - Patrick Stapleton Introduction Twitter GitHhub Blog Angular Class 03:39 - Advantages of Server Rendering 14:28 - Universal & Isomorphic 24:11 - Caching and Load Balancing Rendering the Application Rendering the Application with Data 41:29 - Service Worker 43:02 - Bindings 46:36 - Rendering Angular 49:00 - Prerendering 52:41 - Rendering in Angular 2 58:38 - Time Table Picks 14 by Peter Clines (Lukas) ZPacks Cuben Fiber Arc Backpacks (Ward) Angular Remote Conf (Chuck) Iron Sharpens Iron (Chuck) View from the Top (Chuck) GetHuman (Jeff) Angular Universal (Jeff) Open Source (Patrick) Angular Summit (Patrick) AngularConnect (Patrick)

Sign up for Angular Remote Conf!   02:35 - Jeff Whelpley Introduction Twitter Blog GetHuman Angular Air 02:53 - Patrick Stapleton Introduction Twitter GitHhub Blog Angular Class 03:39 - Advantages of Server Rendering 14:28 - Universal & Isomorphic 24:11 - Caching and Load Balancing Rendering the Application Rendering the Application with Data 41:29 - Service Worker 43:02 - Bindings 46:36 - Rendering Angular 49:00 - Prerendering 52:41 - Rendering in Angular 2 58:38 - Time Table Picks 14 by Peter Clines (Lukas) ZPacks Cuben Fiber Arc Backpacks (Ward) Angular Remote Conf (Chuck) Iron Sharpens Iron (Chuck) View from the Top (Chuck) GetHuman (Jeff) Angular Universal (Jeff) Open Source (Patrick) Angular Summit (Patrick) AngularConnect (Patrick)

FalcorJS and Angular 2 - The one and only Jafar Husain joins us to talk about FalcorJS. Jafar is a tech lead at Netflix and he is on the TC-39 committee. He is also a champion of reactive programming and Observables. Guests: Jafar Husain Panelists: Aimee Knight, PatrictJS, and Jeff Whelpley Picks/Tips: Jafar - Redux, GraphQL, ImmutableJS Kent - First Timers Only, MidwestJS, React Rally Aimee - Nodevember, SparkPost Patrick - Open Source, AngularConnect: Full-Stack Angular with Jeff Whelpley and PatrickJS Jeff - Angular Air 25: Babel vs TypeScript, JavaScript Jabber 168: The future of JavaScript with Jafar Husain Angular Air is a video podcast all about Angular hosted by egghead.io instructor Kent C. Dodds. Please visit the Angular Air website (http://angular-air.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. --- Support this podcast: https://anchor.fm/angularair/support

TypeScript or ES6 with Babel? - Fill-in host Jeff Whelpley along with panelists Patrick Stapleton and Aimee Knight discuss a question that nearly every Angular developer will ask themselves at some point in the next year: Should I use TypeScript or ES6 with Babel? Host: Jeff Whelpley Panelists: Aimee Knight and PatrictJS Picks/Tips: Aimee - Nodevember Conference Patrick - Next Episode on FalcorJS, Do side projects Jeff - No Boston Olympics Angular Air is a video podcast all about Angular hosted by egghead.io instructor Kent C. Dodds. Please visit the Angular Air website (http://angular-air.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. --- Support this podcast: https://anchor.fm/angularair/support

This week Fuhmentaboudit! host Mary Izett takes listeners along to the Windy City for a bottle share gathering that went down at Brew & Grow in Chicago’s West Loop in partnership with the C.H.A.O.S. Brew Club. Chatting up a plethora of homebrewers including Jim Vondracek, Chuck Mac, Kristina Wallig, Paul Thompson, Jeff Whelpley, and Brian Dombrowski, Mary gets the scoop on what each is fermenting these days and what’s to come from the Midwest’s brew barons! This program was brought to you by Union Beer Distributors.

Angular 2 Alpha - Patrick Stapleton, Jeff Whelpley, and Rob Wormald have been using Angular 2 Alpha a bit and will have some insightful things to say about their experience in this show that I think you’ll definitely want to catch :-) Guests: Patrick Stapleton, Jeff Whelpley, and Rob Wormald Panelists: Olivier Combe, Aimee Knight, Scott Moss, and Carmen Popoviciu Angular Air is a video podcast all about Angular hosted by egghead.io instructor Kent C. Dodds. Please visit the Angular Air website (http://angular-air.com) to see upcoming and past episodes. Also be sure to follow Angular Air on Twitter and Google+ to stay up to date with future episodes. Also, all episodes are on the YouTube channel as well. --- Support this podcast: https://anchor.fm/angularair/support

The crew talks isomorphic JavaScript and AngularJS with Jeff Whelpley.

The crew talks isomorphic JavaScript and AngularJS with Jeff Whelpley.

The crew talks isomorphic JavaScript and AngularJS with Jeff Whelpley.