The latest News and Information on Observabilty for complex systems and related technologies.
Any significant shift in an organization’s software engineering culture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development—is no different. Leaning into observability, which calls for tool-enhanced investigation, hypothesis testing, and data richness can be cumbersome even for the most veteran of teams.
Getting a good grasp on your application, especially when it is distributed across multiple clouds, kubernetes clusters and serverless functions is not an easy fit.
Miss O11y is delighted to welcome our newest band member: Martin Thwaites! Martin has been a member of the Honeycomb user community practically since its inception. He is a UK-based consultant who specializes in helping teams scale up and tackle challenging business problems, and a long-time contributor to the Azure and.NET communities. We think he looks ✨amazing✨ in a tiara.
It’s time we had a real conversation about why UX designers everywhere are still unhappy, why that elusive “seat at the table” feels so impossibly out of reach to so many (even at companies that embrace design), and how this impacts your business Design is facing down an epidemic of designers who feel burned out, taken for granted, marginalized, and disrespected. Yes, there is something different about our experience compared to other disciplines.
DevOps: Development and Operations joined together in perfect harmony, one feeding the other and vice-versa. That's the dream. But it's easy for the link between the two to be broken. 'Dev' stops talking to 'Ops,' or Ops falls out with Dev, often because of a lack of understanding of each other's goals. That's where Monitoring and Observability come in. They're like the mediators whose job is to make sure the two main players in DevOps keep that metaphorical dialogue open.
