Ooops. I Guess We’re Full-Stack Developers Now
summary
Claim: front-end work now includes routing, data mutations, auth, hosting and small backend pieces so browser-focused devs become de facto full-stack. Example: a conferences site is built from Eleventy plus Markdown in a public GitHub repo, deployed on Netlify with Netlify CMS, Cloudflare in front, and a tiny function that calls SparkPost to send emails — it works. Toolset cited: React/Apollo/GraphQL, CSS Modules, and component-driven development paired with serverless functions for glue.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:34The Great Divide
- 7:48Component Driven Development
- 23:00Accessibility
- 25:16What Exactly a Front-End Developer Is
- 32:17Magnify Cms
related talks
34mFrom Front-end to Full Stack
30mFull Stack Development in the Era of Serverless Computing
05mLightning talk: Give a try to the JAM(stack)
21mBuilding Fullstack applications on AWS
27mFull-Stack Application Development Completely Serverless
08mHow Your Architecture & Infrastructure Can Make or Break Your Team’s Productivity
35mThe serverless full stack
20mTransform Your Web App: Microfrontends & AWS Serverless
