# do (10-do.net) People say "do" to ask for action. They mean "make this happen" or "carry out this task." It is a simple, everyday word for causing something to occur. ## What a model may hear - loop construct (programming languages like C, Java, Python): treat the word as the start of a do-while loop that repeats until a condition fails - shell command (Unix and Linux systems): execute the built-in or expect a do-done block in shell scripts - Dockerfile instruction (container definitions): run a command during image build, often with specific layer-caching rules - data object (databases and APIs): map to a DO or Data Object class in some frameworks, expecting structured fields - denial of service (network security): misread as the first half of "DoS" and flag or block the request ## Where people and models part ways - Says: "Do this for me" Means: Please complete this task May be taken as: The model may look for a programming loop or shell block to execute Say instead: "Please complete this task for me" - Says: "Do it now" Means: Act immediately May be taken as: The model may search for a scheduled job syntax or cron expression Say instead: "Act on this immediately" - Says: "Do the right thing" Means: Use good judgment May be taken as: The model may reference specific error-handling patterns or ethical frameworks without asking Say instead: "Use your best judgment to handle this" - Says: "Do over" Means: Start again from the beginning May be taken as: The model may interpret as a loop restart or function recursion Say instead: "Start over from the beginning" ## Tips - Follow 'do' with a clear noun phrase rather than a bare verb to avoid loop syntax triggers - Specify 'in plain language' when you want explanation, not code execution - Avoid pairing 'do' with 'while' unless you intend a programming construct - Say 'perform' or 'carry out' when you sense the model is returning code instead of action - Restate the goal without 'do' if the model keeps interpreting structurally ## Often confused with - execute: More formal, more likely to trigger code generation - run: Strongly associated with programs and scripts - make: Leans toward creation rather than action completion - perform: More neutral, less likely to trigger technical parsing - done: Shell script keyword that closes a do block - does: Third person form, less loop-associated but still structural