devopsdays Chicago 2015
2015-08-30..2015-08-31
Chicago, United States
[devopsdays Chicago 2015, DevOpsDays Boston 2016, devopsdays Chicago 2016, DevOpsDays Philadelphia 2016, DevOpsDays Chicago 2017, DevOpsDays Boston 2017, DevOpsDays Philadelphia 2017, DevOpsDays Boston 2018, DevOpsDays Chicago 2018, DevOpsDays Chicago 2019, DevOpsDays Boston 2019, DevOpsDays Philadelphia 2019, DevOpsDays Chicago 2020, DevOpsDays Boston 2020, DevOpsDays Boston 2021, Devopsdays Boston 2022, DevOpsDays Boston 2023, DevOpsDays Philadelphia 2024, DevOpsDays Boston 2024]
who it's for
devops engineers, operations engineers, platform engineers, engineering managers, site reliability engineers, qa engineers, open source contributors
topics
enabling microservices adoption; continuous delivery pipelines; ci/cd pipeline design; chef workflow optimization; monitoring-driven service development; feedback frameworks for ops; postmortem and failure analysis; feature toggle management; ops team structure and hiring; contributing to open source projects
| title | author | length |
|---|---|---|
| State of the DevOps | John Willis | 34m |
Counts and measurements dominate: DevOps Days grows to about 30th devopsdays attendance and roughly 25 events a year; the DevOps Survey jumps from ~1,000… | ||
| Enabling Microservices | Steve Hoffman | 33m |
Extracted a monolithic page into 40+ independent modules and packages each as a Docker image, deploying with Jenkins → Artifactory → Marathon on Mesos, using… | ||
| Building World Class Ops Teams | Charity Majors | 31m |
Bootstraps an ops team only when facing hard problems like extreme reliability or rapid growth, not just to offload boring work; examples include Instagram… | ||
| Brainstorming Failure | Jeff Smith | 25m |
Describes applying Failure Mode Effects Analysis to production monitoring at Grub Hub: assemble cross‑functional teams, map the process, brainstorm every… | ||
| Your Goat Antifragiled My Snowflake | Clinton Wolfe | 06m |
Definitions shift into actionable rules: treat servers as pets vs cattle—automate creation and destruction, don’t hand-tend hundreds; use Chat Ops (Slack… | ||
| LaundryOps - Explaining DevOps to Normal People | Boyd Hemphill | 06m |
Claims that applying continuous delivery to home chores works: adopt one load a day, use an energy efficient washing machine, keep spare capacity so big piles… | ||
| Parental Advisory: Explicit Content | Alina Mackenzie | 06m |
Argues for making work explicit with concrete practices: talk in public so a third person hears and a fourth learns, ask questions to expose unconscious… | ||
| Does QA have a place in DevOps? Heck yeah! | Alejandro Ramirez | 06m |
Argues that QA belongs inside DevOps and gives concrete practices: automation is a must with manual testing limited to exploratory, tests run inside CI/CD… | ||
| What DevOps is Not | Leon Fayer | 06m |
DevOps is specific claims not slogans: not a thing and not a product you can buy—vendors pitch it, but you cannot purchase a complete solution. Hiring a role… | ||
| It's More Than Feature Toggles: ... | Dan Piessens | 36m |
Argues that feature toggles are technical debt and must be codified as enums/classes, tied into CI so every check‑in builds, packages, and deploys a sealed… | ||
| Frameworks for Feedback | Rebecca Miller-Webster | 35m |
Asserts that code reviews are by far the best way to detect error, recommends concrete frameworks — situation behavior impact and mirror empathy validation —… | ||
| The DevOps Pipeline | Steve Pereira | 28m |
Argues that value stream mapping makes DevOps progress tangible by revealing where code stalls and what to automate, showing concrete tools like Jenkins and… | ||
| Day of the Donkey | Michael Coté | 37m |
Conference claim: mainstream IT can become a software‑defined business if organizations stop blaming tooling and fix meatware — people, process and management… | ||
| How the Fork Do I Contribute to Open Source | Trevor Hess | 06m |
Explains concrete steps: use GitHub fork and pull request to send changes back, or submit an issue if you can only report a bug; build small reusable tools or… | ||
| Building Continuous Delivery Pipelines | Surya Gaddipati | 06m |
A pipeline that spins up containerized build slaves on demand replaces brittle pet servers: Jenkins + Docker + Kubernetes coordinate to run tests inside… | ||
| Ten Quick Tips to Improve Your Chef Workflow | Tom Duffield | 06m |
Ten concrete claims and tools: use ChefDK as an all‑in‑one workstation bundle; install Chocolatey, ConEmu and PSReadLine on Windows; put shared test values in… | ||
| Monitoring as a First Step to a New Service | Darron Froese | 06m |
Argument: monitor first, before there is data and before deployment. Prototype uses console and its DNS HTTP key value interface; initial worries about memory… | ||
| Organizational Learning Through Trolling | Michael Stahnke | 06m |
Claim is that deliberate provocation accelerates learning by forcing concrete work not abstract debate. Example: switching from Ruby to a JVM for on‑prem… | ||
| nothing matches | ||