Everything as a Code
summary
Argues that nearly every development task becomes executable code: workstation setup via Ansible playbooks that run with one command, build and packaging with Gradle and Docker images, tests that emit reusable snippets (Spock + Asciidoctor) and load checks with vegeta or JMeter returning 0/1. Describes a three‑step feature rollout (1 server → partitions → all) encoded in YAML, kept in git, and wired into Jenkins pipelines so rollouts, automated tests and rollbacks are reproducible and mostly work in practice.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:38Working environment as code
- 10:02Code build and automation
- 14:56Testing and validation
- 21:54Experiments and deployment
- 27:51Documentation as code
- 33:50Infrastructure as code
- 38:02CI/CD as code
- 46:04Summary and outlook
- 48:12Q&A
related talks
30mEverything as Code
33mOperations: a developer's guide
12mProgressive DevOps approach using Ansible
27mConcept to Code to Runtime - Simplify, Enable, Exploit
01h 02mTools and Techniques for Infrastructure as Code
01h 02mTools and Techniques for Infrastructure as Code
46mImplementing Infrastructure as Code
41mAll Things Continuous