3 ms·

About 15 or so years ago, I was involved in a project to do automatic document generation. The documents that were to be generated were for various clients in v

About 15 or so years ago, I was involved in a project to do automatic document generation. The documents that were to be generated were for various clients in various industries. I won't name the company for various reasons. The idea at the time was to produce a customised document based on client, client industry, products applicable and a few other specified (but varying requirements). The customisation of the document was in the hands of the relevant sales/marketing person involved and was based a that person specifying a range of options (standardised by industry/products). What became obvious over the time of developing this particular systems was that the sales/marketing people were actually not interested in such a facility, even though it would save them many hours producing the documents required. Work undertaken with other companies that had interactions with sales/marketing teams also highlighted that there is a level of distrust with such systems. Over many years, I have had to write user guides, functional specifications, technical specifications and product documentation and even though there may be company standards for such documentation, every document has had much that was not common even in the same class of documents. I don't know if your system would be that helpful to many people. It might be useful for a small class of people. However, I don't think that this would be a useful idea to try and sell, so to speak. Of course, things may have changed in the last ten years.

xqliu 3y ago
Dear, Really appreciate for your sharing. Your experience is exactly what we were thought about .... Over many years, I have had to write user guides, functional specifications, technical specifications and product documentation and even though there may be company standards for such documentation, every document has had much that was not common even in the same class of documents. ---> I think here is where the new LLM can help, it actually can help on prepare most of the contents and build best practice into the document. I don't know if your system would be that helpful to many people. It might be useful for a small class of people. However, I don't think that this would be a useful idea to try and sell, so to speak. ---> Yeah you are absolutely right, we also think that the customer base for such a system is not large. So truth.. though not sounds great.. Really appreciate. We are also thinking about a new approach to help user write doc using AI, by let user to # Create document 1. Input a description 2. GPT to generate a outline based on the description 3. User can interactive with the generated outline, like restructure the outline, change outline title, add / remove outline items etc. 4. And then we will let GPT generating the actual content of each header. # Edit document 1. User can interactive with the generated outline, like restructure the outline, change outline title, add / remove outline items etc. 2. User can input description for instruction, we will combine it together with the structure changes user made on step 1. 3. Then we will ask GPT to generate the actual content of each header. We think that if we can follow the above steps, together with the old content and structure of the whole doc, all send to GPT, GPT will do a great job to write / edit / rewrite the doc, with contents which actually is correct and usable. But also concerning about the token consume... it looks like it will uses many tokens if we really want GPT to have a complete high level insight of the doc and can do a proper adjustment for sub level header. Do you have any suggestion on this scenario? Thanks again for your great sharing :)

xqliu 3y ago

Dear, Really appreciate for your sharing. Your experience is exactly what we were thought about .... Over many years, I have had to write user guides, functional specifications, technical specifications and product documentation and even though there may be company standards for such documentation, every document has had much that was not common even in the same class of documents. ---> I think here is where the new LLM can help, it actually can help on prepare most of the contents and build best practice into the document. I don't know if your system would be that helpful to many people. It might be useful for a small class of people. However, I don't think that this would be a useful idea to try and sell, so to speak. ---> Yeah you are absolutely right, we also think that the customer base for such a system is not large. So truth.. though not sounds great.. Really appreciate. We are also thinking about a new approach to help user write doc using AI, by let user to # Create document 1. Input a description 2. GPT to generate a outline based on the description 3. User can interactive with the generated outline, like restructure the outline, change outline title, add / remove outline items etc. 4. And then we will let GPT generating the actual content of each header. # Edit document 1. User can interactive with the generated outline, like restructure the outline, change outline title, add / remove outline items etc. 2. User can input description for instruction, we will combine it together with the structure changes user made on step 1. 3. Then we will ask GPT to generate the actual content of each header. We think that if we can follow the above steps, together with the old content and structure of the whole doc, all send to GPT, GPT will do a great job to write / edit / rewrite the doc, with contents which actually is correct and usable. But also concerning about the token consume... it looks like it will uses many tokens if we really want GPT to have a complete high level insight of the doc and can do a proper adjustment for sub level header. Do you have any suggestion on this scenario? Thanks again for your great sharing :)