Serverless is other people
summary
Argues that serverless pushes responsibility onto ops as the first last and only line of defense, forcing ops to own security incidents, network misconfigurations, vendor black boxes, and 3rd‑party failure modes. Connects concrete practices—incident playbooks, function-level tracing, and tightened runtime IAM—with cultural shifts: hiring, oncall support, and trauma-aware management informed by experience covering 1,000 startups (188 acquisitions, 28 vanishings, 8 IPOs). Urges engineers to apply distributed systems skills to human problems and cites the value of the psychology of trauma for building resilient teams.
AI-written summary · about
related talks
05mUnleash your DevOps with Serverless
15mThe Ops in Serverless
23mServerless Ops: What to Do / This is What We Do, When the Server Goes Away
24mServerless security: how to protect what you don't see?
04mWhat if serverless was real?
37mLegends and Myths of Security in Serverless
28mApplying the Serverless Mindset to Any Tech Stack
51mConfusion In The Land Of The Serverless