Two Frames on Development and Operations
summary
Frames treat DevOps and serverless as ways of seeing rather than practices, so attention shifts to concrete tradeoffs: bounded versus global rationality, 20% Pareto knowledge overlap between dev and ops, SRE as a boundary-spanning role implementing SLOs not doing the work, and serverless shifting economics to component-level utility and “fin‑dev” so each function gets priced and externalities appear. Expect design conversations about componentization (Herbert Simon’s watchmakers), networks between functions, and who bears the operational cost.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:06What are Frames
- 3:16Information vs X Formation
- 5:10Ontology
- 6:23Arrow Technics
- 8:25retrospective coherence
- 10:00cones of the future
- 13:52reframing
- 14:40intending and attending
- 15:28DevOps as a frame
- 20:14Connection
- 21:19Conjunction
- 25:00Pareto Knowledge
- 26:18Orthogonal Concerns
- 27:14Boundary Spanning
- 29:39Serverless
- 32:39Cognitive Engineering
- 34:41Componentization
- 36:21Utility to Component
- 37:29FinDev
- 40:29Externalities
related talks
24mFinDevOps and Site Reliability in the Serverless Age
05mUnleash your DevOps with Serverless
41mDevOps in a Serverless context, opportunity [...] ?
40mDevOps in the era of serverless computing
32mOps in the Time of Serverless Containerized Webscale
05mDevOps is dead, Servers are dying...
37mTHE DEVOPS EVOLUTION
23mServerless Ops: What to Do / This is What We Do, When the Server Goes Away