Six years of frontend architecture, most of it on surfaces other people depend on daily. React for UI composition. Next.js for the full-stack picture — server components, streaming, and edge deployment. Angular in production at Capital One: reactive forms, lazy modules, a Karma-to-Vitest migration, and a rolling major-version upgrade across every service. RxJS for taming async complexity. Tailwind and SCSS because design constraints are productive constraints. D3 and Three.js for when data needs to become visual — layout math only, React renders the SVG.

Module Federation and micro frontends show up here as an organizational tool rather than a buzzword: at Publicis Sapient in 2017–2019, when the term was still unusual, and again at Capital One as the approved forward direction for the collection-agent UI. Webpack 5 and Vite are the two bundlers that make it work.

Core Web Vitals and WCAG 2.2 close the list because a page nobody can load or read has not actually shipped. Page loads on the SFCC engagements dropped 30–50% through lazy loading and code splitting, and the accessibility work went to AAA.