I wrote a blog post for Honeycomb and shared a little bit about my journey from internal observability champion, to Honeycomb customer, to Honeycomb employee (aka Bee).

In addition to the specifics of my journey and the strategies I used to advocate for improving observability, what I hope you take away is how eminently humanizing it is to work to empower your colleagues and teammates. Observability is most powerful when it is a joint and intersubjective discipline, not one that extols individual prowess or expertise.

In a rapidly evolving software development landscape with shifting practices and increasingly lofty expectations, teams and orgs that can scale their subject matter expertise are the ones that will best be equipped to survive this moment, not individual super debuggers of last resort.

I hope that when you read this, you understand a little bit about why this kind of work matters to me given these conditions.

https://www.honeycomb.io/blog/from-customer-to-bee-observability-champion-journey