Episode

The New DevOps With Adam Jacob

Podcast
Arrested DevOps
Published
Sep 7, 2023
Duration seconds
3490
Processing state
processed
Canonical source
https://www.arresteddevops.com/the-new-devops/
Audio
https://media.blubrry.com/arresteddevops/content.blubrry.com/arresteddevops/arrested-devops-podcast-episode192.mp3
JSON
/v1/public/podcasts/arrested-devops/episodes/the-new-devops-with-adam-jacob
Markdown
/podcast/arrested-devops/the-new-devops-with-adam-jacob.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/arrested-devops/episodes/the-new-devops-with-adam-jacob/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/arrested-devops/the-new-devops-with-adam-jacob.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Adam Jacob, creator of Chef, argues that modern DevOps has failed by prioritizing rigid, factory-like pipelines over real-time human collaboration. He proposes a 'second wave' of tooling that moves beyond automation toward systems that actively facilitate engineering teamwork.

Topics

  • DevOps
  • Software Engineering
  • Automation
  • System Initiative
  • Infrastructure as Code
  • Continuous Delivery
  • Platform Engineering
  • Collaboration Tools

Highlights

  • Main idea: DevOps has transitioned from a collaborative movement to a rigid set of automated pipelines that actually discourage real-time interaction
  • Failure mode: The 'software delivery factory' metaphor has sucked creativity out of engineering by replacing human coordination with asynchronous code reviews
  • Practical takeaway: Effective DevOps requires tooling that pushes engineers together rather than just automating the handoff between them
  • Main idea: The current industry focus on GitOps and CI/CD often ignores the most important metric for high-performing teams: the rate of collaboration
  • Failure mode: Attempting to retrofit modern agile practices onto legacy infrastructure processes creates friction and prevents true agility

Chapters

  1. 5:25 The Origins of DevOps: A look back at the early days of operations and the necessity of cross-functional collaboration.
  2. 9:30 The Necessity of Collaboration: Why application performance and infrastructure security require deep integration between teams.
  3. 14:00 The Rise of Automation: Tracing the history of infrastructure automation from the 1990s to the present.
  4. 18:25 The Stagnation of DevOps: Analyzing why a decade of DevOps evolution hasn't significantly improved engineering outcomes.
  5. 22:55 Tooling as a Catalyst for Collaboration: The argument that tools must be designed to force engineers to work together, not just apart.
  6. 27:05 The Software Factory Problem: Critiquing the pipeline-centric approach that treats engineers like parts in a factory line.
  7. 31:20 The System Initiative Vision: Adam Jacob discusses his new work to create a second wave of DevOps tooling.
  8. 44:25 Challenging the Status Quo: Why the current state of DevOps is unsustainable and why we must rethink the entire system.