13 min · Beginner
Iteration, Debugging, and Refinement
Treat the first answer as a draft of the conversation, name the symptom, and repair only the part that failed.
Learning objectives
- Use a repair menu instead of rewriting the whole brief after every miss.
- Quote the failing lines and ask for a revision of only that part.
- Decide when a fresh chat is safer than another turn in a contaminated thread.
01
Why this matters
The first reply is evidence about your brief, not a final grade. If you rewrite the whole world after one miss, you will not know which sentence caused the trouble. A small repair, or a fresh chat when the thread is contaminated, keeps your time on the work instead of on the theater of starting over.
02
Concept
The first answer is a draft of the conversation, not a verdict on your idea or on the model. Gemini filled the brief you actually wrote, including the blanks you left. Read it the way you would read a junior colleague's first pass: what is usable, what is wrong, and what was never asked. If you throw the whole chat away after one miss, you learn nothing about which sentence caused the miss.
Prompt debugging — name the symptom before you rewrite the world. Pick one label. Too vague: ask for the missing names and the decision. Too long: set a word cap and say what to cut. Wrong audience: restate the reader and what they know. Invented facts: use only the notes, and mark gaps unknown. Generic voice: swap the mood word for two concrete rules. Missed constraint: quote the skipped rule and repair only that.
When one paragraph fails, do not ask for a brand-new answer. Quote the part that failed. Paste the weak lines, say what is wrong in one sentence, and ask for a revision of only that part. Example: the second paragraph invents a budget number. Replace only that paragraph using my notes. Leave the subject line and the closing question unchanged. Partial revision keeps the good sentences stable.
Start a fresh chat — clean context — when the thread is contaminated with a wrong assumption. If the model locked onto the wrong country, the wrong product, or a fact you corrected twice, later turns will keep repeating that error. When the task is fuzzy, ask Gemini to list assumptions before answering, then correct the list, and only then allow the draft. That pause is cheaper than untangling a confident memo built on a guess you never made.
03
Real-world example
Quote the bad weeks, keep the rest
A community tutor asked for a study plan and got a four-week university timetable with invented evening hours. The symptom was invented facts, not a bad subject. The repair did not say try again. It quoted the bad lines: Week 1 through Week 4 assume a six-week clock I never gave you. Replace only that timetable. List assumptions first, and do not write a new plan until I correct the list. Context to add: Form 4 mathematics in Kenya, 40 minutes on weekday evenings, paper in 18 days. Leave any greeting alone. This is prompt debugging in one move. Name the symptom, quote the part, limit the revision, and refuse to let a wrong assumption stay in the thread. If the next answer still talks about university, start a fresh chat.
04
Gemini demonstration
A realistic exchange. Open Gemini beside this page and try a version with your own facts.
You
Write a study plan for my exam.
Gemini
I am assuming you mean a university entrance exam in English, taken in six weeks, with two hours a night free. If that assumption is wrong, the plan below is the wrong plan. Week 1: read a general guide and make flashcards. Week 2: practice mixed questions. Week 3: take a full mock and review every miss. Week 4: repeat the mock and sleep more. This is too vague to use. It names no subject, no country, no exam board, and no real hours. It also invented the six-week clock and the two-hour evenings. Before a better plan, I should list assumptions and wait. The symptom is a fuzzy task, not a weak student.
You
The week plan invented a six-week clock and a university entrance exam. Symptom: invented facts, and too vague. List your assumptions as separate lines and do not write a plan yet. Use only this context: I am preparing a Form 4 mathematics paper in Kenya, I have 40 minutes on weekday evenings, and the paper is in 18 days.
Gemini
Assumptions I will not treat as facts until you confirm them. One: Form 4 means the Kenya Certificate of Secondary Education mathematics paper, not a university test. Two: the 18 days include weekends, and you can study only Monday to Friday, so nine evenings, not eighteen. Three: 40 minutes is the whole session, including review, so new practice must fit inside that window. Four: you already attend class, so this plan does not reteach the whole syllabus. Five: you have past papers available offline. Six: the goal is accuracy on topics you miss, not a new textbook. I am not writing the plan in this turn. Correct any line that is wrong, especially the exam name and the count of evenings.
05
Prompt breakdown
The prompt
List assumptions before you answer. My task is a study plan. Known facts: Form 4 mathematics in Kenya, 40 minutes on weekday evenings, paper in 18 days, past papers are available offline. Do not invent the exam board, the hours, or the topics. Output: a numbered assumption list only. After I confirm, I will ask you to revise a plan. If I say a line is wrong, drop it.
- The first line stops a fuzzy task from becoming a confident plan built on a guess.
- Known facts are separated from what the model is not allowed to invent.
- The output shape is an assumption list only, so a full timetable cannot sneak in yet.
- The last lines tell you the next move: confirm, then ask for a revision, and drop any line that is wrong.
06
Common mistakes
Usually
This is wrong. Start over and do better.
Better
The second paragraph invents a budget. Replace only that paragraph using my notes. Leave the rest unchanged.
Usually
Ignore what I said before about the country and continue.
Better
This thread is stuck on the wrong country. I will open a fresh chat and paste only the corrected facts.
Usually
Just give me the plan. You can guess the hours.
Better
List your assumptions first and wait. Do not write the plan until I correct the list.
07
Practice exercise
Repair one paragraph
Done when: You have a quoted repair, a named symptom, and either a corrected paragraph or a fresh chat with a confirmed assumption list.
08
Challenge
Debug a contaminated thread
Find a chat where Gemini repeated a wrong assumption, such as the wrong country or product. Quote the paragraph that shows the error. Name the symptom from the repair menu, and ask for a revision of only that paragraph. If the next answer still uses the bad assumption, stop and open a fresh chat, a clean context. Paste only the corrected facts. Ask for an assumption list and correct it before you allow a full draft. Then request the deliverable. In your notes, record the symptom, whether you stayed or started fresh, and what you still must verify yourself.
Hint: Name the symptom in the same sentence as the quote. A vague try again usually rewrites the parts that were already fine.
09
Key takeaways
- The first answer is a draft of the conversation, not a verdict.
- Prompt debugging means you name the symptom before you rewrite the world.
- Quote the failing part and ask for a revision of only that part.
- A fresh chat is a clean context when a wrong assumption has contaminated the thread.
10