A Prompt Is a Specification, Not an Assignment
If a question is still open inside the text, the text isn't ready to be handed over. 👋 Hi — I'm Anton, a software engineer working mostly in PHP/Symfony and Go, currently carving a live PHP monolith into Go services. This part is about the thing I hand over when I hand over work: the text itself. It's one habit from one codebase — maybe it's useful to you, maybe you already do it better, maybe…
In the realm of software development, a prompt serves as a specification rather than an assignment. This distinction is crucial in the execution model the author employs, characterized as "done and forgotten." In this model, an executor is given the entire task in a single message and operates without referencing any other information. Once the task is completed, there is no lingering context or communication between the executor and the task. Each task is independent, with no connection to previous or future tasks.
The author emphasizes that an assignment outlines what should come out, leaving the executor to gather the necessary facts. In contrast, a specification includes the facts within itself, specifying who pays for the information and how many times it should be accessed. This distinction has significant implications for the execution process, as it determines the resources required and the potential for errors.
The author explains that the "done and forgotten" model relies on a clear understanding of the task at hand, without the need for follow-up questions or discussions. An open question within the text can be problematic, as it implies that the task is not yet complete. The author advises against using phrases like "considerate phrase" or "adjust if needed," as these can introduce ambiguity and hinder the execution process.
To ensure clarity and efficiency, the author suggests including specific details in the text, such as exact paths, full signatures of types and interfaces, existing primitives, values (not descriptions), and a single acceptance command. These elements serve to minimize the need for additional research and reduce the likelihood of errors.
In summary, a prompt in the author's work is a comprehensive specification that provides all the necessary information for an executor to complete a task independently. By adhering to this approach, the author aims to streamline the development process, minimize ambiguity, and reduce the potential for errors.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
