Skip to main content

Episode 3 - DevOps

Overview​

Is DevOps a role or a culture? In this episode, we discuss what DevOps is and how DevOps theory may differ with DevOps in practice.

info

Watch this episode on Youtube.

Tech News​

The news articles we looked at on stream:

  • “Thinking in Systems: A Sociotechnical Approach to DevOps”

    • Key Points:
      1. DevOps needs a holistic approach that considers both technical tools and organizational factors.
      2. Complexity in development can be tackled by adopting tools that provide a holistic view of service dependencies and value chains.
      3. Empowering developers with agency and creating an environment conducive to deep work are crucial for successful DevOps.

Presentation​

Full Slide Deck available on request. Alt text

  1. What is DevOps?
  2. Software Lifecycle
  3. Theory vs Practice
  4. Challenges and Benefits

What is DevOps?​

"DevOps a culture designed to break down barriers between Software Developers, Operations and other parts of an organization"

Alt text

Software Lifecycle​

Alt text

Theory vs Practice​

Alt text

In practice, DevOps has become an entire role that bridges the gap between Development and Operations. This new role is responsible for all the tools and processes that in theory, should be owned by both the Dev and Ops teams.

Are we just shifting the bottleneck or is the newly created DevOps Engineer role unblocking the SDLC? It depends on company size, existing company culture, stakeholder buy-in and the DevOps tools that you use.

Challenges and Benefits​

Alt text

Alt text

Demo​

Ron took us through the CI/CD pipelines for his digital garden using GitHub Actions. Check it out below 👇🏽