22.03
item · Curriculum / Frontend

Applied Angular

New Angular applications start fast. Then features that were easy early on get harder: internal coupling, inconsistent state management, and ad hoc API calls start to collide, and the tests get brittle. User-facing code changes constantly, and it also has to absorb changes in backing services that may not be maintained by the same team.

This course is about keeping the line level. We start with an existing application and look for what’s going wrong (hidden side effects, duplicated API calls, rendering problems, confused routing, inconsistent UI) and refactor each one. Then we build the patterns that prevent them: centralized side effects and data fetching, routes as the source of state, components and directives as the application’s own business language, and team conventions for sharing code and keeping dependencies current.

Who it’s for

Mid-level and senior Angular developers working on a team. You should know the general ontology of Angular (components, routing, services) and be comfortable with TypeScript, the Angular CLI, VS Code, and basic Git. Beginning Angular is the usual path here.

How it runs

Four days, live and online, with the current release of Angular. Explanation, live coding, and hands-on practice, with plenty of room for questions and discussion.

What you’ll be able to do

  • Find the code smells that slow an Angular application down, and refactor them.
  • Centralize API access and side effects, and validate what comes back.
  • Use signals and observables to keep the UI in sync, with routes as the primary source of state.
  • Secure routes, and know where route guards stop protecting you.
  • Design components and directives that express the business, not just the layout.
  • Agree on team conventions for sharing code, branching by abstraction, and keeping dependencies up to date.
  • Structure an application that doesn’t get more brittle as it grows.
22.03
Topics
22.03
Full topic list
Every topic in the course: for searching, and for checking against what your team needs.
→