Master Angular Signals
A hands-on course that takes you from your first signal() to leading a team's reactive architecture. Every concept comes with a live playground you can poke, break, and rebuild.
A Note of Caution This is an AI generated course that I built for the purpose of trying to learn about signals. I cannot verify the accuracy of the content until I have completed the course myself. Please use this course as a starting point for your own learning and research.
I will update the content as I learn more about signals and Angular.
Read a little
Tight explanations focused on the mental model, not API dumps.
Play a lot
Every module has live, editable demos wired to real signals.
Prove it
"Your turn" exercises with acceptance checks you can verify.
The learning path
The reactive primitive and everything built directly on it.
What is a Signal?
Reading, writing, and the mental model of reactive values.
Computed Signals
Declarative derived state that recalculates only when it must.
Effects & Side Effects
Running code in response to change — and when NOT to.
The signal-based component authoring APIs.
Signal Inputs
input() and input.required() replacing @Input.
Two-Way Binding with model()
Building components that participate in [(banana-in-a-box)].
Signal Queries
View and content queries as signals, with explicit timing and boundaries.
Writable derivations, RxJS interop, and loading data.
linkedSignal()
Writable derived state with explicit reset and preservation rules.
Signals ↔ RxJS Interop
toSignal, toObservable, and picking the right tool.
Async Data with resource()
Signal-native loading, error, and reload for async work.
Stores, zoneless performance, testing, SSR, and lead-level judgement.
Signal-Based State & Stores
Structuring shared state in services — and when to reach for a library.
Zoneless Change Detection
How signals drive rendering once zone.js is gone.
Testing Signals
Unit-testing signal state, computeds, effects, and components.
Lead-Level Patterns & Anti-Patterns
Judgement: what to reach for, what to avoid, and why.
SSR, Prerendering & Hydration
Running signals on the server, and surviving the handover to the browser.