4 ms·
As good as slack is for communicating I don't think it should be used as a "knowledge" store. At a previous employer I found that commit messages were a great w
by mdergosits 11y ago
As good as slack is for communicating I don't think it should be used as a "knowledge" store. At a previous employer I found that commit messages were a great way to store information. Maybe commit messages aren't as great for question and answers, but searching slack doesn't seem very intuitive.
Idea: A slack bot that searches for questions and answers and creates a wiki out of the scraped information.
- Jemaclus 11y agoWhat's really great is when you go back in the Slack history from the day you interviewed and see what people said about you... I imagine that can sometimes be awkward.
- toomuchtodo 11y agoPrivate email should always be used for chatting about potential hires, instead of Slack.
- torbit 11y agosounds like they are using it wrong. user error.
- gohrt 11y agoOr privacy fail in the applicatio design/UI
- fluxquanta 11y ago>As good as slack is for communicating I don't think it should be used as a "knowledge" store. It's not that it shouldn't be, but that it probably won't be when it should. My company uses HipChat and not Slack, but ever since we first adopted it about 4 years ago I have been preaching that our in-house technical support staff use its search function before asking the developers for help. Maybe 10% of them do, if I'm being generous. The rest think their issue is unique and requires immediate one-on-one developer attention. We also have an in-house wiki that doesn't get consulted as often as it should. I spend at least half a day documenting, from a end-user perspective, every project I complete on our wiki and still find myself repeating what I've written in a one-on-one chat on a daily basis.