ยฉ 2026 Hashnode
๐ 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

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...

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...

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...

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...

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...

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...

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...
