5d ago · 9 min read · 👋 Welcome to Chapter 4! Buckle up — this is the chapter that trips up even experienced developers. But don't worry. By the end, it will make total sense. The question today is: What do you do when yo
Join discussion
Mar 21 · 9 min read · "pipe() and Operators — The Superpowers of RxJS" 👋 Welcome to Chapter 3! So far you know: Observable = a stream of data (Chapter 1) subscribe = how you receive data (Chapter 2) Now here's the re
Join discussion
Feb 7 · 4 min read · When I first started working with Angular, component communication was one of the most confusing aspects of the framework. I'd find myself passing data through multiple levels of components, creating complex event chains, or resorting to global state...
Join discussion
Feb 7 · 3 min read · When I first started building Angular applications, I thought I needed Redux or NgRx for state management. Then I realized that Angular is built on RxJS, and I could manage state effectively using just Observables, Subjects, and BehaviorSubjects. Thi...
Join discussion
Jan 26 · 2 min read · Are you struggling to scale your enterprise applications, or feeling overwhelmed by complex state management and folder structures? Learn how to design large-scale enterprise Angular applications with an industry expert (Manfred Steyer) in an immersi...
Join discussion
Jan 21 · 7 min read · A few years ago, some very smart developers on my team solved a problem Angular hadn't addressed yet: how do you handle async state cleanly across an enterprise application? Their answer was elegant. A ResponseService that wraps any observable into a...
Join discussion
Jan 7 · 5 min read · Let's be honest — I've written allowSignalWrites: true more times than I'd like to admit. Every time, it felt like a hack. Every time, I told myself I'd come back and fix it properly. Then last week, I actually did come back. There it was — code I de...
Join discussion
Jan 6 · 5 min read · Few weeks ago, I couldn't explain why I'd choose a signal over a BehaviorSubject. Today, I just built an entire component without a single subscribe(), takeUntil(), or ngOnDestroy(). No Subjects. No lifecycle hook juggling. Just signals, computed val...
Join discussion
Jan 5 · 6 min read · I need to show you something embarrassing. This is a pattern I've written in almost every component that needed reactive inputs: private metricInSubject = new ReplaySubject<DashboardMetricWithVisualization>(1); @Input() set dashboardMetricWithVisuali...
Join discussion
Jan 3 · 6 min read · I have a confession. When I first learned about effect(), I thought: "Oh, this is just subscribe() with a nicer API." And I started using it everywhere. Signal changes? Effect. Need to do something? Effect. Want to compute a value? Eff— wait, no. Tha...
Join discussion
