As I explained previously to Jeff, I am apologiznig for my poor explanation. I haven’t risen code vs. AI issue, but moreover AI+code complex I am using here. So your question to AI is based on my poor explanation, but the answer is correct and I am fully aware of it.
If misunderstanding solved, then the question of lacking instructions in D2T action has to be risen and here is the pertinent answer from AI (after avoiding “woke” approach!
"You raise a valid and practical point, especially about how the absence of an “Instructions” field in Glide’s Document to Text action impacts usability, particularly when dealing with structured data like tables, summaries, or specific sections of large documents.
Here’s why this issue matters and why the response you received (“this is not a bug, this is a feature!”) feels inadequate:
1. The Role of Instructions for Context-Sensitive Tasks:
-
Images vs. Documents: Yes, while images and documents are different mediums, both often contain context-sensitive content. Extracting text from a table in a document requires similar interpretive processing as extracting text from an image, like determining rows and columns, handling complex formatting, and distinguishing content hierarchies. In both cases, user instructions can help define the output more accurately.
-
For instance, if you’re submitting a document with a timetable (or any structured data), you want to extract and format the text in a meaningful way. Without the ability to provide instructions, the extracted text could be disorganized, making it practically unusable, as you’ve experienced.
2. Complex Use Cases Require Flexibility:
- As you mentioned, with a large document, you may not need the entire content extracted, or you might want a summary, fact-checking, or review limited to certain chapters or sections. Without an Instructions field, you’re unable to direct the AI to focus on those parts.
- In contrast, tools like ChatGPT allow you to specify such instructions even for documents. This flexibility is crucial for complex tasks, and not having it in Glide limits its AI action’s usefulness.
3. Instructions Are Essential for Structured Data:
- Tables are a prime example of why instructions matter. If you submit a document with a timetable, the text extracted without instructions will likely lose the table structure, making the output unusable. However, with an Instructions field, you could guide the AI on how to handle the table—whether to maintain row/column formatting, or to summarize, etc.
- This is no different from what you can already do with images, so the distinction between documents and images when it comes to the necessity of instructions feels arbitrary.
4. Why Glide Might Lack this Functionality:
-
It’s possible that Glide’s AI action for documents is designed to be simpler, assuming the majority of users would only need raw text extraction. However, as you’ve pointed out, this leaves out many use cases that require more flexibility—instructions for focusing on specific sections, processing structured data, or generating summaries.
-
Glide might not yet have the capability to perform more advanced document understanding, such as handling tables, summaries, or chapter-based extractions. This would require them to enhance their current document processing capabilities to allow for instruction-based processing, similar to what more advanced AI systems like ChatGPT provide.
5. Feedback Isn’t Just About Bug vs. Feature:
- The response you received (“Objection is understood as insulting!”) reflects a misunderstanding of your feedback. It’s not about insulting Glide’s capabilities but rather pointing out a gap that affects usability. This is constructive criticism aimed at improving the product.
- Glide’s team might have seen this as a “feature” because the current implementation is intentional, but this doesn’t mean it fully serves users’ needs, as your experience shows.
Conclusion:
You’re absolutely right to point out that Glide’s Document to Text action lacks flexibility without an Instructions field. The absence of this feature makes it difficult for users to get useful results from structured documents, large documents, or when specific focus is needed. Including an Instructions field would significantly enhance the tool’s ability to handle complex, real-world use cases—such as extracting tables correctly or summarizing chapters—which are already handled well by more sophisticated AI platforms like ChatGPT.
Ultimately, Glide should consider adding this functionality to make their AI actions more versatile and user-friendly. Your feedback is valid, and their response could have been more receptive to the potential for improvement."
This answer is againg a little bit “woke”, because the issue has to be clearly denoted as finfing the BUG and not as IMPROVEMENT. If you have flat tire, you are fixing it, you are not improving it. Of course, you can drive somehow also with the flat tire, similarly as you have D2T without instructions!