# put (1-put.us) People say "put" when they want something placed somewhere. They might say "put it on the list" or "put my appointment at three." It means move, save, or set. ## What a model may hear - HTTP PUT request (web APIs and REST design): treat the word as a command to overwrite a resource at a specific URL, expecting complete data and an exact location - file put operation (FTP, SFTP, and cloud storage tools): initiate an upload to a remote server or bucket, often requiring credentials and paths - database put (key-value stores like Redis or DynamoDB): store or replace a value by key, sometimes with TTL or consistency settings - shell put command (expect or Tcl scripting): send output to a process or format a string, rarely seen in modern shells - options trading put (finance and trading platforms): interpret as a contract to sell at a set price, triggering portfolio or risk calculations ## Where people and models part ways - Says: "put this somewhere safe" Means: save my file securely May be taken as: overwrite an existing resource without asking, or fail because no URL was given Say instead: "save a copy of my file with a new name and tell me where it went" - Says: "put it at the top" Means: make this the first item on my list May be taken as: send an HTTP PUT to a root path '/' and replace the whole site or document Say instead: "add this to the beginning of my numbered list" - Says: "put my answer in the chat" Means: include this information in your reply May be taken as: attempt to POST or PUT to an external API endpoint that does not exist Say instead: "include this information in your next message to me" - Says: "put everything together" Means: combine these ideas into one summary May be taken as: merge data structures by overwriting keys with matching names, losing information Say instead: "combine these points into one paragraph without leaving anything out" ## Tips - Say 'save' or 'store' instead of 'put' when you want something kept for later. - If you mean a list or document, say 'add to' or 'insert into' rather than 'put'. - Avoid 'put' followed by a web address; the model may try to send data there. - Say 'overwrite' or 'replace' explicitly if that is what you want; do not assume 'put' conveys this. - Use 'combine' or 'merge' when you want things joined, not placed. ## Often confused with - post: adds to a collection rather than replacing at a specific location - set: configures a value or property, not always stored persistently - place: more physical or spatial, less likely to trigger HTTP or database actions - save: clearly means persist to disk or memory without overwrite assumptions - push: adds to a stack or queue, or forces to a remote repository - patch: sends only changed fields, not a complete replacement