3 ms·
> 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 con
by 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 agoYou'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!"