10 May 11:15 — 12:00
About the session
For years, testable systems have helped us amplify flow, feedback, learning and experimentation. Testable software doesn't assert the health of our business transactions in production.
Observability is the testability of the 2020s, finally shifting our attention right.
Software is becoming more observable by the builders themselves. Observable systems democratise the understanding of systems where analytics have fallen short.
I have experienced first-hand how building observable systems is a socio-technical practice. This is the story of what we learnt in the last three years of maturing observability practices.
- How observability – as of equivalent importance to testability – is a catalyst for enabling and empowering teams to build better software sooner.
- What it really takes to go from one person advocating for observability to the whole company adopting it as part of the golden path.
- What practices and tooling you need and how they evolve.
- What practices emerge as a result.
- How observability practices and tooling is eating the world of analytics and data intelligence
This talk has not been given before; it’s addressed to all disciplines: engineering, product, delivery, agile coaches, design, UX, data, analytics, etc. My goal is to start a public discourse about what observability actually enables: engineers thinking about observability first means that we end up with reliable telemetry data and platforms all disciplines can use to understand our systems in production. It will not be an advanced technical talk; the focus will be on the practices it enables and the mindset of flow, feedback, learning and experimentation it enables.
Observability, Testability, Engineering Practices, Agile Practices, DevOps, Analytics, Data, Flow, Feedback, Experimentation, Learning