DevOps for Frontend Engineers
summary
Argues that DevOps applies to client-side work and gives concrete wins: a React Native pipeline redesign caches iOS artifacts and swaps a JS bundle to cut build time from 5 hours to 5 minutes; use OpenFeature for progressive rollouts, canary releases and kill switches; instrument client telemetry with web core vitals, OpenTelemetry, Prometheus/Grafana and tools like InsightHub for tracing; favor fast integration tests over flaky E2E, run Lighthouse and accessibility checks on preview branches, and measure deployment frequency and cycle time.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:11In inferiority complex for backend developers
- 6:40Frontend vs frontend
- 9:30What is DevOps
- 10:38Sunshine in production
- 14:01DevOps a team effort
- 18:46Flowbased development
- 26:37Reduce development time
- 28:29Split tasks into manageable chunks
- 30:12Deploy more frequently
- 33:07Feature toggling
- 36:05Observability
- 40:55Tracing
- 45:35Testing
- 54:30DevOps Culture
related talks
42mDevOps for Frontend
19mDevOps for Frontend: beyond Desktop Browsers
28mDevOPs Lessons for Frontend Developers
46mDevOps for Java Developers (or maybe against them?!)
32mDevOps for Vue developers
37mDevOps, 12 Factor and Platform Engineering
41mDevOps for Java Developers (or maybe against them?!)
37mDevOps for Java Developers (Or Maybe Against Them?!)