Operations: a developer's guide
summary
Explains concrete practices: use configuration management (Puppet or Ansible) so servers are cattle not pets, bring up reproducible VMs with vagrant up and inspect them via vagrant ssh, prefer Make for repeatable build tasks, and treat Docker as optional now rather than urgent. Shows a six‑command Unix pipeline that counts most‑frequent words, argues testing on identical local VMs prevents case‑sensitive and dependency bugs, and reports these approaches work in production.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:23Anna Shipman
- 0:53My First Job as a Proper Developer
- 1:13Redirecting Urls
- 4:28Shared Hosting
- 5:41What Happens if Your Server Dies
- 6:09Configuration Management
- 6:33Configuration Management Tools
- 7:24Getting Started Guides
- 8:35Virtualization
- 9:03What Hypervisor Is
- 11:29Advantages of Using Cloud Computing
- 12:31Hardware Accelerated Virtualization
- 13:03Vagrant
- 16:57Containerization
- 18:21Virtualization versus Containerization
- 18:59Configuring a Virtual Machine
- 23:30Tools To Make You a Better Developer
- 24:00Task Runners
- 24:43Advantages of Make
- 29:31Stream Editor
- 30:52Reading the Output
related talks
34mDevops or: How I Learned to Stop Worrying and Love the Ops Team
25mDevOps for Pointy-Haired Bosses
25mDeveloper Experience is central to DevOps success
57mGo Away Or I Will Replace You With A Very Little Shell Script
59mEverything as a Code
53mGround Truths of a Rugged DevOps Practitioner
24mTaming Your Inner Cowboy Coder - A Simple And Sane DevOps Workflow
32mLooking Back At 13 Years Of DevOps