Frontend

Brad Frost's methodology for composing UIs from a hierarchy — atoms, molecules, organisms, templates, pages.

The shared language of product UI — design tokens, component libraries, documentation, and the governance that keeps them alive.

What happens between URL and pixels — parsing, the rendering pipeline, the event loop, and the process/security model.

Core Web Vitals and the loading/runtime budgets behind them — measuring real users, then fixing what the metrics actually point at.

The type system as a design tool — structural typing, narrowing, generics, the strictness dials, and types that make invalid states unrepresentable.

Building interfaces that work for everyone — semantic HTML first, ARIA as the escape hatch, keyboard and focus discipline, and testing that catches what tools miss.

How UI code stays sane as it grows — one-way data flow, composition patterns, and the discipline of putting each piece of state where it belongs.

Where HTML gets made — CSR, SSR, SSG, streaming, islands, RSC — the cost model of each, and the meta-frameworks that package the trade-offs.

CSS as an engineering discipline — the cascade tamed with layers and tokens, layout owned via flexbox and grid, and the methodology debates settled by trade-off.

Testing UIs without testing the framework — behavior-first component tests, network mocking at the boundary, E2E for the money paths, and visual regression for the rest.

The house hexagonal reference realized for the browser — an npm workspace of per-context module packages, custom elements as the driving adapters, every browser API behind a driven port, the WCCG Context protocol wiring ports from each app shell's assembly point, and an import map deduplicating element-defining packages across micro-frontend bundles.

The layered TypeScript toolchain — runtimes, package managers, compilers, bundlers — across the frontend and backend worlds, and the artifact formats they produce.

Practice material: katas, challenges, build projects.