[jbay808]

By "that stuff", do you mean "technical communications you have had with colleagues", such as what Slack or email might otherwise be used for? That is what the GP was referring to.

It's hard to imagine using a wiki for that, but if that's how you do things I guess it's fine. As long as it doesn't rely on people copying their email discussions to wikis manually. Not sure how you'd be alerted by an important wiki update that you need to respond to, though.

[icedchai]

Let's use a concrete example. A new engineer joins your company and needs to set up a dev environment. This environment has changed many times over the years. Do you point them to Slack, Email, a Wiki, or a shared Google doc? In any sane company, it is one of the latter.

[jbay808]

Replying a little late, but we are discussing

"technical conversations I have had with my colleagues where I can go to recover details I might not remember from a month ago. Then again email also does this just fine, and doesn't cost as much."

For static instructions like setting up a dev environment? Sure a wiki is perfect. But I don't use a wiki for technical conversations like "Hey icedchai, I'm getting an error message that the COM port is not detected and I remember you said something about solving it in yesterday's standup. Can you point me to where the fix was?"

That message is better suited for slack or email than a wiki. (Your solution might be in the wiki but I'm contacting you because it wasn't easy to find, or searching for the error message didn't turn it up).

But if I use email, then when we hire a new employee a month later who gets the same error, your answer will be in my records but not theirs.

Another poster suggested a mailing list, that is a good option that makes email viable for this.