4 ms·

I get that people want this, I just don't get why. After 20 years of work as a sysadmin/coder/DBA, I've never even remotely wanted this. Documentation is the

I get that people want this, I just don't get why. After 20 years of work as a sysadmin/coder/DBA, I've never even remotely wanted this. Documentation is the key. Wikis. Code comments. Bug/issue trackers. I've never considered walking up to someone's desk, and talking to them, as something I need documented, and searchable. And that's what slack/irc/IM/etc is to me. Walking up, and talking to someone at a desk. Not to mention, if you want any REAL functionality with Slack, you have to pay. And you thereby outsource all backups, and additionally loads of confidential conversations to an external company. Which then cuts you off if you cancel your account! Most of the people I know who use Slack, use it "because that's why SV uses".

Turbots 6y ago
There you have it. You're a sysadmin. Indeed you never need help from anyone, you're happy to work the same way for 10 years and not change a damn thing.
zimpenfish 6y ago
> Documentation is the key. Wikis. Code comments. Bug/issue trackers. That requires people to write them and unless there's a strong managerial hand poking constantly, it's often "there's no time right now, we'll do it tomorrow" and, as we know, tomorrow never comes.
- bbarnett 6y ago
  You're certainly describing failed managerial methods. And employees who aren't very good at their job. Yet Slack isn't really the answer. Frankly, Slack is inept management's attempt to fix their own, and employee's, shortcomings. Having a new on-board use some search function on Slack, to look through 100s of hours of conversation for "random important things", isn't going to fix that. Nor will people sifting through that junk, help when some bonehead didn't backup, or document key vital parts of a config. Or code. If it's important, it needs to be documented. Not be stuck in a deluge of endless blather, random docs, zero real version control, the list goes on. Ah well.
  - zimpenfish 6y ago
    > Having a new on-board use some search function on Slack, to look through 100s of hours of conversation for "random important things", isn't going to fix that. Just been through that and I 100% agree. Unfortunately my push for "everything needs more documentation" has not succeeded because "we don't have time to document stuff!"

Turbots 6y ago

There you have it. You're a sysadmin. Indeed you never need help from anyone, you're happy to work the same way for 10 years and not change a damn thing.

zimpenfish 6y ago

> Documentation is the key. Wikis. Code comments. Bug/issue trackers. That requires people to write them and unless there's a strong managerial hand poking constantly, it's often "there's no time right now, we'll do it tomorrow" and, as we know, tomorrow never comes.

bbarnett 6y ago
You're certainly describing failed managerial methods. And employees who aren't very good at their job. Yet Slack isn't really the answer. Frankly, Slack is inept management's attempt to fix their own, and employee's, shortcomings. Having a new on-board use some search function on Slack, to look through 100s of hours of conversation for "random important things", isn't going to fix that. Nor will people sifting through that junk, help when some bonehead didn't backup, or document key vital parts of a config. Or code. If it's important, it needs to be documented. Not be stuck in a deluge of endless blather, random docs, zero real version control, the list goes on. Ah well.
- zimpenfish 6y ago
  > Having a new on-board use some search function on Slack, to look through 100s of hours of conversation for "random important things", isn't going to fix that. Just been through that and I 100% agree. Unfortunately my push for "everything needs more documentation" has not succeeded because "we don't have time to document stuff!"