read
To look at written words and understand them. To take in a book, article, or message with your eyes and mind.
What a model may hear
- file read operation operating systems and programming
- open a file and return its bytes to a program, possibly with buffering, encoding detection, or permission checks
- database read query databases and backend systems
- execute a SELECT or equivalent fetch, possibly choosing between primary and replica nodes
- memory read computer architecture and hardware
- transfer data from RAM or storage into CPU registers, with cache implications
- read-only mode system administration and DevOps
- treat a filesystem or service as immutable, blocking any write or mutation
- read receipt messaging protocols and email
- send or request a notification that a message was opened by the recipient
Where people and models part ways
“I read it”
Meant: I looked at and understood the text you sent
May be taken as: assume the user performed a system read operation and ask for file paths or byte counts
Say instead: “I have read and understood your message”
“Can you read this?”
Meant: Please look at this text and tell me what you think
May be taken as: attempt to parse it as code or data format, or ask for file permissions
Say instead: “Please review this text and share your thoughts”
“I want to read more”
Meant: Give me additional information or longer content
May be taken as: offer to increase buffer size, page size, or database fetch limits
Say instead: “Please provide more detail or continue with additional information”
“Read it back to me”
Meant: Repeat what I just said so I can check it
May be taken as: dump raw file contents, log output, or memory state
Say instead: “Please repeat my last message back to me”
Tips
- Say 'review' or 'look at' when you want analysis, not 'read' if you mean critique
- Specify 'aloud' if you want spoken output, since 'read' alone may trigger silent processing
- Use 'summarize after reading' to avoid getting raw data dumps
- Say 'I have read' instead of 'I read' to avoid past-tense parsing confusion
- Add 'for meaning' or 'for content' to steer away from technical file operations
Often confused with
- parse
- structural analysis, not comprehension
- fetch
- retrieval without understanding
- scan
- quick surface look, not deep reading
- load
- into memory, not into mind
- consume
- processing or using up, often of data streams
- render
- displaying, not interpreting