8 ms·
There’s so much value in consistent, expertly-written technical documentation that outsourcing it to the hallucination machine is a pointless exercise in aggrav
by ndespres 1y ago
There’s so much value in consistent, expertly-written technical documentation that outsourcing it to the hallucination machine is a pointless exercise in aggravation. I do not wish to read machine-mangled slop. I want an expert to write expertly.
- kaycebasques 1y agoThis doesn't create slop. It's just an automated editor. A linter for natural language.
- smarx007 1y agoI am afraid the choice in many OSS projects is not slop vs expert-written content but LLM-assisted content or nothing. I recently produced a bunch of migration guides for our project by pointing Claude 4 Sonnet at my poorly structured Obsidian notes (some more than 5 years old), a few commits where I migrated the reference implementation, and a reasonably well-maintained yet not immediately actionable CHANGELOG. I think the result is far from top-notch but, at the same time, it is way better IMO than nothing (nothing being the only viable alternative given my priorities): https://oslc.github.io/developing-oslc-applications/eclipse_lyo/migration-5x-6x/ https://oslc.github.io/developing-oslc-applications/eclipse_...