Angular's working parts, talked through by a panel.
Adventures in Angular brings together a changing panel and a guest developer to talk through the framework's working parts, from push-based change detection to NGXS actions and RxJS retry logic. None of the code is visible, so every idea has to hold up when it is explained in plain speech, with room for easy banter at the edges.
PRESS PLAY
Adventures in Angular is a numbered, panel-driven series about the Angular framework, and its back catalog runs deep. Most installments bring in one developer as a guest. The panel around them shifts. Aaron Frost introduces himself as host in 'Migrating Material: AngularJS -> Angular with Michael Prentice - AiA 410', with Joe Eames and Brian Love on the panel. In the Azure Cognitive Services episode, Alyssa Nykle does the introductions, with Brooks Forsyth alongside her as panelist. The conversations stay close to real implementation detail. The Push Pipe episode with Michael Hladky frames push-based change detection against the async pipe, which it places in a pull-based approach: an HTTP request emits, parent components get marked for check one after another, and the application re-renders downward. The explanation also notes that plain promises work as well as observables. The Joaquin Cid episode compares NGXS with NgRx. In NGXS, an action can call an API such as Firebase and patch the state from a single block of code, while the NgRx side of the conversation splits that work across effects and reducers. One participant repeats the idea back to confirm it landed. That habit of checking understanding aloud is a large part of the appeal. Nobody can see the code. A closing remark in one episode admits as much, noting that people sometimes ask to show code no listener could ever see. So the ideas have to be carried in speech. A discussion of the RxJS retry operator hangs on one clean distinction: a promise is an execution already under way, while an observable is closer to a formula for subscribing, which is why retry has everything it needs to try again. Practical tradeoffs get airtime too. Ankit Sharma describes an Angular client that uploads an image for OCR and shows a preview, working within a four-megabyte cap set by the API. In the Brad McAlister episode, the panel talks through turning off view encapsulation so CSS cascades normally, and one speaker admits that NX slowed onboarding for new developers while a giant global SCSS file stayed put. The mood is friendly rather than formal, and that same episode closes with jokes about adding a panelist and who has already been kicked off. For a first listen, 'How to Get a 60% Performance Gains with Push Pipe featuring Michael Hladky - AiA 438' is the natural starting point for anyone drawn to change detection.
Made for: Suits a listener who already works in Angular and wants to hear other developers reason through state libraries, RxJS operators, component styling and change detection in conversation.
What sets it apart: Suits a listener who wants Angular explained through spoken reasoning rather than slides. Guests talk through change detection and state flow without visuals, and the panel asks clarifying questions and compares the ideas with its own setups.
Join our weekly discussion about how to build top end Angular applications and become an Angular expert. Become a supporter of this podcast: https://www.spreaker.com/podcast/adventures-in-angular--6102018/support.
A giant SCSS file walks into an Angular component; your styling argument finally has company.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A grounded Angular episode on component styling, global CSS, view encapsulation, and the theming choices teams actually face.
Angular component styling gets treated here as a real architectural decision, not a neat rule to memorize. The conversation follows the tension between scoped component styles and the global CSS that still shapes an app, especially in an Nx setup where components may live in…
A concrete walkthrough of how a push-based change detection idea carries an HTTP result through Angular.
Angular performance becomes easier to grasp when it follows one HTTP request through a component tree. The discussion sets Angular's pull-based flow beside a push-based approach, tracing how an observable or promise reaches the async pipe, marks parents dirty through…
A practical NGXS and NgRx comparison that keeps API calls, payloads, and patchState close to the code.
NGXS gets a focused run-through here, as the conversation weighs its state model against NgRx and follows the path after an action is dispatched.
A useful explanation of how RxJS retry can rerun observable work after an API failure.
This episode gives the retry operator a practical shape through a discussion of why observables and promises behave differently when failure enters the picture.
A practical tour of an Angular and .NET OCR app where usability choices matter as much as the API call.
Ankit Sharma walks through a practical Angular and .NET OCR app that lets a user upload an image, sends it to an OCR API, and returns extracted text in the UI.
Power Platform news with practical static.
This episode continues a discussion on advanced patterns with Angular directives, featuring a return guest expert.
Brad McAllister describes Storybook as a sandbox for Angular components, where "knobs" let him test disabled states, icon variants, and button sizes without waiting on a full app refresh.
Michael Vlodky says the push pipe skips the full Angular path and calls "detect changes" on one component only.
Joaquin Cid says NGXS actions can be asynchronous, so Firebase queries and state updates live in one block.
Jason Akbar says `debounceTime` can stop an API from firing on every keystroke.
Ankit Sharma, a Google Developer Expert and full-stack developer at ADP in Hyderabad, India, walks through an Angular plus ASP.NET Core OCR app that calls Azure Cognitive Services.
Armin Vardanyan, a senior front-end developer and team lead at Armenia's Volo, describes four years working with Angular, starting when Angular 2 was in beta.
Ravi Veliyat describes Angular component communication through inputs, outputs, and singleton services.
Philip Kief explains how Angular interceptors and a global error handler can catch front-end and HTTP errors.
Nishu Goel, an IBM developer and Google Developer Expert in Angular, explains that IBM's "garage" setup, with clients moving from two months of Angular to five months of React, led her to export reusable components as web components.
Gil Fink, CEO of one-person firm Sparksys, describes profiling as acting like "a CSI guy or girl" who finds bottlenecks and memory leaks, with a target of 60 frames per second.
Adventures in Angular episode 429 maps front-end state tools like Redux and NgRx onto back-end event sourcing, where "a hundred percent of your state is based on those events." Guest Luis Galeas, founder and CEO of Ambar, explains why back ends need persistent, pre-processed state per user, unlike a front end that can rebuild after pressing F5.
A panel of Angular experts discuss web development, including a Cypress webinar and Angular consulting.
The host discusses a scheduling issue and upcoming plans, then introduces a course on getting a job in tech.
A panel discussion on building design systems using Angular, featuring guest developers sharing their experiences.
An interview with a senior front-end developer about his experience with Angular, from its beta to current version.
A weekly discussion about building top-end Angular applications, featuring interviews with experts and panel discussions.
This episode discusses building enterprise applications with Angular, featuring an expert guest author of Angular for Enterprise books.
A panel discussion with a guest about Angular development and related tools.