3 ms·
There's a cultural/process hack that can really help here: be meticulous about turning questions in Discord into updates to your documentation. If you do that,
by simonw 3y ago
There's a cultural/process hack that can really help here: be meticulous about turning questions in Discord into updates to your documentation.
If you do that, Discord can be a powerful accelerant to the quality of your project documentation. But you have to be disciplined about it!
- le-mark 3y agoThis is the key. If I have to do my job and monitor slack discord mattermost all day, I’m not doing my job. Unless my job is support. It’s just one more instance of software development taking over yet another business area (support) because developers are by and large naive, opinionated, and eager to please. It happened with agile (we got project management) and devops (we got sysadmin). Ymmv.
- hobo_mark 3y agoSurely an LLM could parse the chat and keep a public FAQ up to date? Somebody must already have implemented this, but last time I looked I still came empty handed...
- Karunamon 3y agoFrom some experiments with a discord bot, the non-deterministic responses you get from an LLM are the big killer for that use case. Ask the model to summarize 100 lines of chat 10 times and you will get 10 different outputs, all worded subtly differently, with different headlines missing each time. (Even on state-of-the-art GPT-4)
- raidisco 3y agohttps://recurai.com/discord https://recurai.com/discord
- xigoi 3y agoYeah, if you want to have an inconsistent documentation with lots of subtle and non-subtle errors, using a non-deterministic black box to generate it is a great way to achieve that.