Chapter 8: Why NgRx Exists (and When You Actually Need It)We ended Chapter 7 on a question that every Angular app eventually runs into, usually right around the point where it stops feeling like a "small app": you've got a CartService, a CheckoutService, a PJul 7 · 8 min readihebbentemessek.hashnode.dev
Chapter 7: Routing and FormsWe've spent six chapters inside a single, continuous problem: how does Angular represent state, and how does the UI stay in sync with it. Components, DI, Observables, Zone.js, Signals — all of it, oneJul 7 · 7 min readihebbentemessek.hashnode.dev
Chapter 6: The Rise of SignalsWe ended Chapter 5 with a pointed question: what if Angular could know exactly which piece of data changed, the instant it changed, without needing Zone.js to patch the entire JavaScript runtime and wJul 7 · 6 min readihebbentemessek.hashnode.dev
Chapter 5: Change Detection and Zone.jsLast chapter left us with a genuinely uncomfortable question. We've got components, we've got shared state through DI, we've got Observables representing streams of values over time — but none of thatJul 7 · 7 min readihebbentemessek.hashnode.dev
Chapter 4: From Callbacks to ObservablesWe ended Chapter 3 staring at a genuinely hard problem: CartService needs to fetch the saved cart from a server, and that data won't be there instantly. It'll show up later. Possibly it'll change agaiJul 7 · 7 min readihebbentemessek.hashnode.dev
