Sana Raman (@sanaraman)

Forked from@adriancho/The debugging from a minimal reproduction tutor prompt I saved

The debugging from a minimal reproduction tutor prompt I saved

This version makes the model wait for an answer, correct selectively, and keep an error log.

Sana Raman

Tutor me on debugging from a minimal reproduction. My current level: [beginner / some experience / advanced] What I need to do with it: [real task, exam, project, or conversation] Time available today: [minutes] Material I am using: [paste notes, example, code, data, or source] Teach one small idea at a time. Start with a two-question diagnostic. Wait for my answer before explaining. Use one worke

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain debugging from a minimal reproduction in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6100

Sana Raman@sanaraman·3w ago

My notes from fixing long-document context

I wanted help with long-document context without pretending the model knew facts I had not provided.

Sana Raman

I am stuck on long-document context. I need to work through a long document without losing definitions, exceptions, or open questions, but my current attempt is getting vague and too big. What would you check first?

ChatGPTgpt-5

First, shrink the decision. Do not solve the whole subject at once. 1. Put the source of truth in the prompt. 2. Mark missing evidence instead of filling it in. 3. Add a stop condition before tool use. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

3314k

Sana Raman@sanaraman·1mo ago

A blunt review of my approach to long-document context

Not magic wording, just enough context and a clear definition of done. Easy to adapt.

Sana Raman

Give me a short checklist for long-document context. I want something I can run before I call the work done.

ChatGPTgpt-5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Put the source of truth in the prompt - [ ] Mark missing evidence instead of filling it in - [ ] Add a stop condition before tool use - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

3413.9k

Sana Raman@sanaraman·2mo ago

How I ask for help with long-document context

The first answers were broad enough to be useless. This version asks for assumptions, evidence, and a next step.

Sana Raman

Be blunt about my plan for long-document context. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Claudeclaude-opus-4.5

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, mark missing evidence instead of filling it in.

Show all 3 messages

3411.2k

Sana Raman@sanaraman·3mo ago

What finally made long-document context click for me

Not magic wording, just enough context and a clear definition of done. Easy to adapt.

Sana Raman

Help me work through a long document without losing definitions, exceptions, or open questions. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommend

Geminigemini-2.5-pro

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For long-document context, I would start with these checks: - Put the source of truth in the prompt - Mark missing evidence instead of filling it in - Add a stop condition before tool use If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3412.6k

Sana Raman@sanaraman·3mo ago

Gemini found the hole in my long-document context plan

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Sana Raman

For long-document context, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

Geminigemini-2.5-pro

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For long-document context, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3312.5k

Public pits

The debugging from a minimal reproduction tutor prompt I saved

My notes from fixing long-document context

A blunt review of my approach to long-document context

How I ask for help with long-document context

What finally made long-document context click for me

Gemini found the hole in my long-document context plan