The Unix Way Seen by a DevOps
summary
Shows how the KISS Unix philosophy concretely influences modern DevOps by tracing historical failures (e.g., Multics) to design choices and by mapping specific tools—chroot, make, Vagrant, Docker, Git—and techniques (pipes, text-based protocols) to current practices. Explains using containers as infrastructure-as-code, gives an example of replacing a faulty kernel component to stop Linux 2.4 crashes, and argues these Unix patterns scale up into orchestrators and cloud platforms.
AI-written summary · about
chapters (30)
- 0:00Conference intro
- 1:26Infrastructure history
- 4:15WWII and software
- 6:04Mechanical to digital
- 8:35Miniaturization and 2nd-gen
- 10:223rd to 4th gen computers
- 12:30Cold War and tech
- 14:38Infrastructure complexity
- 16:05Unix and KISS
- 18:36Multics failure and Unix
- 20:22Unix philosophy
- 22:11Modular software
- 23:40Unix pipes and microservices
- 25:28Change cost in architecture
- 26:52Linux 2.4 kernel
- 28:17Lightweight tools and agile
- 29:21Chroot and containers
- 30:23Linux and open source
- 32:10Cathedral vs bazaar
- 34:16Agile feedback
- 35:40Git and code
- 37:08GitHub and open source
- 37:50Heroku and containers
- 38:54Software crisis and cloud
- 40:38Human errors in systems
- 41:42VMs and containers
- 42:49Containers for automation
- 43:52Systemd and automation
- 45:39Future of containers
- 47:04Resources and conclusion
related talks
24mEvolution of Unix environments and the road to faster deployments
16mDevOps - Philosophy vs Practice
05mAll I need to know about DevOps I learned from XKCD
33mOperations: a developer's guide
29mDevOps in containerized world
33mDevOps and the Rebirth of Childhood Innocence
56mDevOps in a containerized world
40mDistilled Abnormal DevOps Iterations