{
  "id": 16006031,
  "title": "Don't write the prompt. Get interviewed",
  "url": "https://urgent.news/2026/10/22/dont-write-the-prompt-get-interviewed",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-22T06:03:54.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/hram/dont-write-the-prompt-get-interviewed-hp7"
  },
  "original_language": "en",
  "account": "Writing prompts can be intimidating. Individuals often glance at a lengthy sample complete with constraints, formats, and edge cases, then close the tab, believing they cannot produce something similar. To overcome this challenge, one should consider an alternative approach.\n\nInstead of directly creating a prompt, engage in an interview with the agent. Request them to delve into the stack, architecture, and the limits of the decisions involved. By posing a series of targeted questions, you can gather valuable insights that would have otherwise required extensive prompt writing.\n\nFor instance, inquire about the behavior of the system when the portal is open in multiple tabs simultaneously. This approach helps uncover potential issues that might not be evident through a traditional prompt.\n\nFurthermore, be aware of potential mistakes made by the agent. In this case, the agent initially focused on integrating with PaperLedger before examining the code. Recognize that not all questions are equally important, and prioritize those that address critical aspects of the project.\n\nOnce you have gathered sufficient information through the interview, it becomes easier to construct the scenario, define boundaries, and establish contracts between the components. This information acts as a foundation for creating the final prompt, eliminating the need to write it from scratch.\n\nTo initiate the process, use a simple \"get started\" command. The agent will then take charge, building the app, transitioning to the Python portal, and establishing the connection between the two sides. By following this method, the decisions you would have made naturally emerge in the written document.\n\nThe entire interview process, including the agent's subsequent actions, can be found in the article: [https://hram.github.io/en/articles/mobile-ledger/](https://hram.github.io/en/articles/mobile-ledger/).",
  "summary": "Everyone teaches you to write prompts. In practice, a person looks at a sample a couple of pages long, with a stack, constraints, formats and edge cases, and closes the tab: there's no way I'll write that. I needed a document camera: an Android phone on a tripod above the desk, a live preview in the PaperLedger browser page and a \"Capture\" button. Instead of a technical specification I told the…",
  "key_points": [
    "Instead of writing prompts, conduct an interview with the agent.",
    "Ask targeted questions about system behavior and decision limits.",
    "Use interview insights to construct the final prompt."
  ],
  "editors_take": "Treating AI agents as interview subjects replaces the intimidation of prompt engineering with a collaborative discovery process that uncovers technical constraints and builds a foundation for complex instructions.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}