Oops–I guess we’re full-stack developers now.
summary
Claim: front-end developers are effectively full-stack now because UI work absorbs routing, data fetching, and mutations. Examples: building an SVG icon component inside a component tree that reaches the URL level; fetching and updating data via GraphQL data mutations; wiring view, build, and style with React + Webpack + CSS Modules. Tools shown include serverless and Node patterns, component-driven design, and attention to accessibility and perceived performance on the browser canvas.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:37The Great Divide
- 12:33Mutating data? State management?
- 14:18LAMP Linux Apache MySQL.PHP
- 17:37One of the criticisms of full-stack developers is that they end up doing some parts of the stack badly.
related talks
40mThe Frontend Is a Full Stack
52mWhy Full-Stack Is the Future of Web Application Development
06mFullstack can be fun (again)
45mDo Frontend Devs dream of Backend functions?
41mWhy Full-Stack Is the Future of Web Application Development
21mDante’s Inferno of Fullstack Development (A Brief History)
35mDiscussion: Frontend or Fullstack
16mThe time to go full stack is now