The easy way to Full Stack
summary
Shows concrete wins: add pipeline scripts to auto‑check commit IDs and lint rules, plug renovate boat to auto‑update deps, and reshape scattered API responses on the backend instead of patching the frontend. Implements a backend cache that drops suggestion latency from 2 seconds to 200 millisecond. Syncs types to avoid runtime nulls using a Gradle generator or by adopting nextjs + trpc so changes are reflected instantly. Points out an unsanitized tenant parameter as a real security bug to fix.
AI-written summary · about
chapters (9)
- 0:00Full stack opportunities
- 1:15Full stack roles in big companies
- 2:42Automating frontend tasks
- 3:45API data structure optimization
- 4:53Caching backend responses
- 5:58Debugging type mismatches
- 7:23Synchronizing frontend and backend
- 8:29Frontend role in API security
- 9:57Why full stack knowledge advances careers
related talks
26mMaking internets great again - a story of working with legacy code
14mReact on the Jamstack
23mReact & the JAMstack
45mDo Frontend Devs dream of Backend functions?
10mFullstack Framework for Next.js
38mExplosive Velocity with a Modern Stack
58mDevOps for Frontend Engineers
05mLightning talk: Give a try to the JAM(stack)