Web & Frontend
What the browser actually does with your code — rendering strategies across React, Vue, Svelte, Astro and Next, and the performance budget each one spends.
- Rendering strategiesStatic, server-rendered, streaming, client-rendered and incrementally regenerated pages, compared on one timeline instead of by adjective — when the byte arrives, when the pixel arrives, and when the click actually works.
- ReactReact's rerender-and-diff model, measured in browser work and shipped bytes.
- VueVue's proxy-tracked updates and the dependency graph they create.
- AngularAngular's signal- and component-tree update model, with its explicit costs.
- SvelteSvelte's compile-time component updates and the runtime work they leave behind.
- AstroAstro's server-first HTML and explicit island boundaries for client work.
- Next.jsNext.js's React server/client boundary and the cost of crossing it.
- NuxtNuxt's Vue universal rendering and payload boundary between server and browser.
- State managementDecide where frontend state belongs, how it moves, and when a shared store is the wrong answer.
- StylingBuild predictable, responsive interfaces by treating CSS as a constraint system rather than a pile of overrides.
- Forms and validationMake forms helpful in the browser while keeping the server as the authority over accepted data.
- Web performanceTrace loading and interaction costs to measured budgets under stated network, device, and cache conditions.
- AccessibilityMake interface meaning, focus, input, and feedback available across keyboards, assistive technology, and varied presentation.
- Frontend testingTest browser behavior and component contracts at the boundary where users observe the interface.