Ananya Iyer

Answered What is a sane way to version prompts alongside application code?

Assume injection succeeds and design so that it does not matter. Do not give the model a capability whose misuse you cannot tolerate — no unbounded tool calls, no raw SQL, no sending mail on its own authority. Everything else is defence in depth: mark untrusted content clearly, never let retrieved content look like instructions, validate outputs against a schema, and require a human confirm anything that writes. Delimiters alone stop the lazy attempt and nothing more.

Shared a bide Turn a One-Paragraph Feature Idea Into a Lean PRD

Expand a one-paragraph feature idea into a lean PRD with non-goals, testable acceptance criteria, edge cases, a guardrail metric and open questions.

Shared a bide Explain a Statistical Result in Plain English, Honestly

Translate a study result into plain English: every statistic defined, relative risk turned into absolute numbers, and common misreadings corrected.

Asked a question How do you keep generated code from silently ignoring an edge case?

The generated implementation is usually right for the main path and quietly wrong at the boundary — empty array, single element, duplicate key. I have started asking for the edge cases to be listed before the code, which helps. Is there something better than that, short of writing the tests myself first?