Thread by @mipsytipsy

I too have been meaning to post this blog by @daiyi. It might sound like just another boring feature launch ("woo, search!"), so let me explain why it's step one of the single biggest product and strategic bet of our year, and you should care about it.
. honeycomb.io/blog/how-to-le…

But first: think back to how you first learned to computer. How did you learn? Was it a chore, or was it exciting, delightful, a means to an end?

Most of us learned by tinkering around in low risk environments. We learned from our peers, and we learned because it was *fun*.

I personally learned most of what I know about Unix by reading other people's .bash_history files and running the commands to see what they would do. Until I copied someone running `man` something.

Learning how to run and manage distributed systems can be just as fun and interesting as it was learning to admin individual nodes.

We spend a lot of time at honeycomb thinking about how our tools can help you learn *your own systems* in a safe and playful way.

And this means tapping into our essential nature as social beings.

We LOVE peacocking and showing off for each other. We LOVE imitating someone who knows more than we do to see what sacred wisdom they have. When you turn learning into a social activity, it feels like a game.

It's also a way better source of signal than any AI or ML algorithm can serve up.

What queries/graphs do you want to look at after getting paged -- the one your AI suggests, or the ones from your team mate who most recently debugged this problem?

If I get paged about a service, and it looks like a Kafka problem, but I don't know much about Kafka; but I know there was a similar outage two weeks ago, and liz was the one who debugged it?

Then I want to see what questions liz asked two weeks ago involving Kafka, obviously ☺️

I want to see what services were involved, what comments she left, what queries she tagged in any post mortem boards, or what she posted to slack during that time.

I might trawl through the history of a couple other known Kafka experts on the team for useful queries too.

We don't build for single users, we build for collaboration first.

(Tho you also collaborate with your own past and future selves -- expertise in any system tends to decay after a month or two. "What was that super obvious thing I used to do...?". ✋-- everyone)

Anyway, that's why search matters so much. And you'll see that you can search not just by comments, but by user, time frame, query dimensions, boards saved to, and more.

Specifically designed to help you mine your team history and shared tribal knowledge.

We are working on ways to help teams level up at their systems and learn from each other, and ambient awareness -- that gray area between "wake someone up" and "things are fine" that systems spend most of their time in.

If this sounds interesting to you: ui.honeycomb.io/signup

And now you know why I'm excited about search. ☺️. Oops and I tagged the wrong daiyi -- congrats to @daiyitastic and team, whose ability to translate my inchoate yearnings into real solid product remains a marvel to me. ❤️🐝