DevOpsDays NYC 2020
2020-03-03..2020-03-04
New York, United States
[DevOpsDays NYC 2016, DevOpsDays NYC 2018, DevOpsDays NYC 2020, DevOpsDays NYC 2023]
who it's for
platform engineers, software engineers, site reliability engineers, engineering managers, security engineers, data scientists, observability engineers
topics
production readiness checklist; structured distributed tracing; model deployment and ML pipelines; modular Terraform modules; threat modeling and SAST/DAST; resilience engineering practices; CI/CD pipeline libraries; reliability scoring in Grafana; feature-flagged canaries; failure weeks and pre-mortems; centralized secrets with Vault; when you don't need Kubernetes
| title | author | length |
|---|---|---|
| Welcome and Intro | stefano mueller, jay destro | 11m |
Morning logistics and rules: the code of conduct is enforced with a phone number and email for organizers, closed captions by Two Sigma, and hand‑washing art… | ||
| Are you ready for production? | Janna B. Dogan | 20m |
Explains concrete production readiness: a Google PRR–style checklist that names deliverables for design & development, configuration management, observability… | ||
| Observability for Developers: How to Get From Here to There | Christine Yen | 29m |
Argues that observability benefits developers more than operators and shows how teams move from grepping logs to structured traces with concrete wins: a… | ||
| Productionalizing Data Science Models | Rachael Ferguson | 05m |
Claim: notebooks are not production code and must become maintained artifacts. Practical steps: convert notebooks to pure Python and put code in git; save… | ||
| Don't Fail Fast. Learn Faster | Quincy Iheme | 06m |
A 2x2 chart maps Learning (low→high) against Blast Radius (low→high) and classifies experiments as wasteful, ugly, redeemable, or beautiful. Examples are… | ||
| Infrastructure Changes, So Modularize and Version Your... | Michael Wytock | 06m |
Argues that concrete module boundaries and strict versioning stop churn: use Terraform-style outputs so split modules by build, e.g. networking -> compute ->… | ||
| DevSecOps is a Misnomer | Victoria Geronimo | 06m |
Argues that "DevSecOps" mislabels the work and shows exactly where security sits across plan→code→build→test→deploy→operate→monitor with 1 slide overlaying… | ||
| Can Resilience Engineering be sufficiently described in 5...? | John Allspaw | 06m |
Asserts the title question is answered: “no” — resilience engineering is a 20-year multidisciplinary field now being applied to software, not reducible to high… | ||
| CI/CD Agility and Controlling Pipeline Sprawl | Angel Rivera | 20m |
CI/CD pipelines get unmanageable when YAML configs multiply across repos, so the concrete fix is to extract common steps into reusable modules: an s3 upload… | ||
| Day 1 | 05m | |
Multiple vendor blurbs assert measurable capabilities: AppDynamics claims it maps technical performance to business outcomes across the SDLC; Datadog says it… | ||
| Lessons in Ethical Development I Learned From Star Wars | Jameson Hampton | 34m |
Examples and concrete tools decide whether to watch: the story of Galen Erso and Project Celestial shows how promises of renewable energy become the Death… | ||
| Reliability Scoring: A 3-Part Formula for Promoting Reliable Code | Chen Harel | 26m |
A 3‑part formula scores releases 0–100 by penalizing new errors, rate increases and slowdowns, aggregates penalties into a single reliability score, and plugs… | ||
| 10 years of #devops, but what did we really learn? | Kris Buytaert | 27m |
Ten years of DevOps yields a few concrete facts: a global meetup scene grows to 70 events worldwide with 250 events before and ~900 organisers on Slack, lots… | ||
| Day 2 | Chris Irwin | 04m |
Cloud vendors parade concrete products and claims: SolarWinds offers an integrated APM SaaS family — Pingdom synthetic checks, AppOptics distributed tracing… | ||
| Cooperative Economics for Engineers; or, Why You Have ... | James Meichle | 26m |
Tech history ties concrete practices to current tech labor: medieval guilds using apprenticeship and self‑inspection to guarantee quality; merchant contract… | ||
| Why Events & People Matter: How the new girl used ... | Sheanika Crawford | 06m |
A practical playbook for reviving internal events: uses rapid feedback surveys, iterative agenda changes, added receptions, games, photo booths, upgraded… | ||
| Unquantified Serendipity: Diversity in Development | Quintessence Anx | 06m |
Argues that adding varied backgrounds increases problem solving by changing structures not fixing people, with concrete practices: stop rescuing and instead… | ||
| You Probably Don't Need Kubernetes | Mofi Rahman | 05m |
Claim: Kubernetes is useful but often unnecessary; adoption adds configuration and operational debt, does not make apps faster, and does not magically fix… | ||
| All Tech is Debt | Dave Stanke | 05m |
Claim: all tech is debt — code is obsolete from the minute it ships, carries vulnerabilities like a looming zero day exploit, and loses market value in about… | ||
| Keeping Calm When the Sky is Falling: Reducing Stress around ... | Tom Elliott | 05m |
Claims a practiced plan cuts incident stress and shows it works at Yext after two years of running an incident process. Concrete tools and practices: anyone… | ||
| Product Management for Platform Engineering: Why it ... | Jessica Fredican | 24m |
Argues that embedding product management into platform engineering moves work from vague tasks to measurable outcomes: sets a 95% success rate target for… | ||
| Raffles and Prizes | 12m | |
A run of vendor raffles gives away tangible prizes and one big number: dozens of items claimed onstage including Amazon Echo Alexa, multiple Nintendo Switches… | ||
| The Lifecycle of A Service | Matt Stratton | 24m |
A practical blueprint for owning a service end to end: define a service boundary and name components for what they do, record intent and dependencies, version… | ||
| Low-Context DevOps: Helping DevOps find answers faster | Thomas A. Limoncelli | 30m |
Claims that high‑context team pain (new hires and oncall engineers stuck without instructions) resolves when documentation is made low‑context: incremental… | ||
| nothing matches | ||