[mattlondon]

When someone finds a problem, you raise a bug with reproduction steps, then either fix it or put it in the backlog. Even if it is a document bug. This way anyone - even people not in that chat - can find it.

This is normal operating procedure everywhere: write stuff down. It was how everyone did things before chat was digital, and how they do now too.

If people are relying on searching chat history for how to fix things or get things working, then you are working at a cowboy outfit where quality must suck. I am not saying google the ideal here - I have no insider knowledge there - but fuck dude using chat history to document and maintain your system? Jesus.

[aprdm]

Having joined a company that uses Slack for the first time it was crazy how good it was on searching for issues that other people had. I can quite literally copy and paste the error message above and see other people that had the same issue and how it got solved or not on a thread. I can also bump the thread or go to the channel or reach out to who answered.

It’s pretty great and one of the amazing things on having a lot as chat, it also allows you to easily reach out to anyone very quickly and feels more personal than a ticket in some archaic bug system that becomes a black hole after it gets introduced.

Be careful with your assumptions - it’s not like Google has created much of value in the past N years with its current culture, its original culture (book how Google works) seems much more like the cowboy you criticize