The things I've seen, how DevOps is evolving in practice (Keynote) - Jabe Bloom

Discover how Jabe Bloom's keynote explores the evolving principles of DevOps, transforming operator capabilities, and aligning infrastructure and development to improve overall systems understanding and practice.

Key takeaways
  • DevOps is evolving to focus on making operators better by understanding software practices in operations.
  • There are two types of capabilities in an organization: operations and infrastructure, and development and software architecture.
  • DevOps is a way to think about working in systems, handoff between Dev and Ops, and taking a more scientific approach to working across departments.
  • The way we frame problems can shape our understanding of them, and actively reframing problems can lead to new solutions.
  • Cognitive estrangement is the ability to notice when others’ perspectives differ from our own.
  • Patterns and common components can reduce complexity and improve understanding of systems.
  • Infrastructure and operations can be rethought to align with developer workflows.
  • Socio-technical architecture is important for understanding how social systems and technical systems interact.
  • Pace layering is important for understanding how different layers of a system can move at different speeds.
  • Observability and microservices are important for understanding how systems work.
  • FinOps is important for understanding financial feasibility and economic factors in systems.
  • The “wall of confusion” can be reframed as an opportunity for conversation and discussion.
  • Conversations should be based on purpose and understanding.
  • Isolating valuable parts of an application and encouraging common reuse can improve systems.
  • Science can be applied to understanding systems and improving them.
  • Transition design is important for understanding how social systems and technology interact to change the way we organize.
  • Making people who work on a system better developers is a key goal of DevOps.
  • The constraint moves as organizations adopt DevOps practices.
  • Infrastructure, platform, and software layers should be integrated and managed together.
  • Managing work should be done through flexible teams that combine disciplines.
  • Metrics should be used to measure the people and process portions of the DevOps experience.