The Modern Full-Stack: Owning Your Deployment Pipeline
summary
Argues that being truly full stack requires owning deployment, integration, infrastructure and observability, not just front end and back end. Shows concrete artifacts: Dockerfiles, Kubernetes YAML, Ansible playbooks, templatized scripts, CI pipelines and monitoring. Recommends Jenkins, Argo CD, Terraform, Ansible, Prometheus, Grafana and hands-on practice that gets teams from zero to production. Claims that with 10–12 developers handle production outages once everyone can deploy into a cluster and recover with logs and alerts.
AI-written summary · about
chapters (12)
- 0:00Modern full-stack intro
- 1:03Traditional full-stack limits
- 2:50Developer fears
- 4:36Breaking silos with deployment
- 5:38Deployment automation practices
- 7:24Config files as code
- 9:11Infrastructure templates
- 10:40Secure & observable systems
- 12:27DevOps journey steps
- 13:31DevOps skills roadmap
- 14:36Starting imperfectly
- 15:18Q&A
related talks
30mMoving beyond DevOps with automated cloud-native platforms
41mAll Things Continuous
45mBecoming a Plumber: Building Deployment Pipelines
27mThe curious case of the DevOps engineer and other things ...
27mThe Five Phases of DevOps
34mDeploy, Release, CI/CD, Oh My! DevOps for the Rest of Us
28mThe Only Thing That Matters In DevOps Is...
51mApplication Stacks for the Modern World