Eventually the quality drops to such a level that some poor bastard spends their time bringing it all back up to standard - and the cycle repeats.
Gaining that trust is really hard. The documentation needs to be safe to read, in that it won't mislead you and feed you stale information - the moment that happens, people lose trust in it.
Because the standard of internal docs at most companies is so low, employees will default to not trusting it. They have to be won over! That takes a lot of dedicated work, both in getting the documentation to a useful state and promoting it so people give it a chance.
> Step one, write the documentation yourself.
> Step two, bots hit your website hundreds of times per minute.
> Step three, users never come to your site, they use OpenAI's site.
> Step four, ??? openAI profits
1. Write plan 2. Ask Claude to review for understandability 3. Update as needed until it's clear 4. Execute the task(s) in the plan.
I'm finding Claude gets much further on the first pass. And I can version the plans.
emil_sorensen•4h ago
esafak•4h ago
mooreds•4h ago
We see a surprising number of folks who discover our product from GenAI solutions (self-reported). I'm not aware of any great tools that help you dissect this, but I'm sure someone is working on them.
0: Generative Engine Optimization
nlawalker•44m ago
jilles•3h ago
corysama•2h ago
arscan•2h ago
bobbiechen•2h ago
https://stytch.com/blog/if-an-ai-agent-cant-figure-out-how-y...
QRY•1h ago
I'm in the process of learning how to work with AI, and I've been homebrewing something similar with local semantic search for technical content (embedding models via Ollama, ChromaDB for indexing). I'm currently stuck at the step of making unstructured knowledge queryable, so these docs will come in handy for sure. Thanks again!
shafyy•27m ago