#coding prompts and AI conversations

The using property-based tests tutor prompt I saved

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

Micah Ellis

Tutor me on using property-based tests. 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 worked example,

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain using property-based tests 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

6215k

Haruto Abe@harutoabe·2w ago

finding duplicated state in React: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Haruto Abe

I want to learn finding duplicated state in React, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain finding duplicated state in React 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

6214.5k

Ben Brooks@benbrooks·2w ago

React state that keeps drifting: the version with actual constraints

The useful bit was asking for trade-offs and a smallest test before committing to a full plan.

Ben Brooks

Give me a short checklist for React state that keeps drifting. I want something I can run before I call the work done.

Claudeclaude-opus-4.5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Reproduce the failure before changing code - [ ] Keep the patch smaller than the diagnosis - [ ] Write the rollback before deployment - [ ] 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

3302.8k

Samir Shah@samirshah·2w ago

My notes from fixing a safe dependency upgrade

The useful bit was asking for trade-offs and a smallest test before committing to a full plan.

Samir Shah

I am stuck on a safe dependency upgrade. I need to plan a major dependency upgrade with compatibility checks and a rollback path, 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. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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

3402.3k

Anya Volkov@anyavolkov·2w ago

What I was getting wrong about reviewing code written by an agent

Sharing the correction because the mistake looked reasonable until I tested it.

Anya Volkov

I want to learn reviewing code written by an agent, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain reviewing code written by an agent 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

6312.9k

Felix Silva@felixsilva·2w ago

The cache invalidation without folklore prompt I actually kept

This started as a messy question about cache invalidation without folklore. The follow-up made the answer practical.

Felix Silva

Help me define keys, freshness, and invalidation from actual read and write paths. 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 recommendation. Otherw

ChatGPTgpt-5

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 cache invalidation without folklore, I would start with these checks: - Reproduce the failure before changing code - Keep the patch smaller than the diagnosis - Write the rollback before deployment If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3303k

Anika Kim@anikakim·3w ago

The checklist I use for Postgres query tuning

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

Anika Kim

I am stuck on Postgres query tuning. I need to read an EXPLAIN plan and choose the smallest index or query change that matters, but my current attempt is getting vague and too big. What would you check first?

Claudeclaude-opus-4.5

First, shrink the decision. Do not solve the whole subject at once. 1. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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

3303.8k

Eva Kovac@evakovac·3w ago

The designing idempotent background jobs tutor prompt I saved

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

Eva Kovac

Tutor me on designing idempotent background jobs. 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 worked

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain designing idempotent background jobs 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

6413.2k

Aya Lin@ayalin·3w ago

The question that cleaned up database migration rehearsal

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

Aya Lin

Help me turn a risky schema change into staged, measurable deployment steps. 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 recommendation. Otherwise, s

Claudeclaude-opus-4.5

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 database migration rehearsal, I would start with these checks: - Reproduce the failure before changing code - Keep the patch smaller than the diagnosis - Write the rollback before deployment If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3403.3k

Talia Ibrahim@taliaibrahim·3w ago

API error handling, minus the vague advice

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

Talia Ibrahim

Give me a short checklist for API error handling. I want something I can run before I call the work done.

Geminigemini-2.5-pro

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Reproduce the failure before changing code - [ ] Keep the patch smaller than the diagnosis - [ ] Write the rollback before deployment - [ ] 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

3402.7k

Samir Shah@samirshah·4w ago

A blunt review of my approach to a safe dependency upgrade

This started as a messy question about a safe dependency upgrade. The follow-up made the answer practical.

Samir Shah

Give me a short checklist for a safe dependency upgrade. 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 - [ ] Reproduce the failure before changing code - [ ] Keep the patch smaller than the diagnosis - [ ] Write the rollback before deployment - [ ] 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

3304.2k

Fatima Saleh@fatimasaleh·3w ago

planning a zero-downtime migration: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Fatima Saleh

I want to learn planning a zero-downtime migration, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain planning a zero-downtime migration 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

6412.7k

Adrian Cho@adriancho·3w ago

The learning TypeScript at runtime boundaries tutor prompt I saved

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

Adrian Cho

Tutor me on learning TypeScript at runtime boundaries. 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 w

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain learning TypeScript at runtime boundaries 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

6213.1k

Rowan Blake@rowanblake·4w ago

testing API failure paths: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Rowan Blake

I want to learn testing API failure paths, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain testing API failure paths 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

6213.9k

Lucia Marin@luciamarin·3w ago

What I was getting wrong about debugging from a minimal reproduction

Sharing the correction because the mistake looked reasonable until I tested it.

Lucia Marin

I want to learn debugging from a minimal reproduction, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-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

6412.7k

Mina Cruz@minacruz·4w ago

How I ask for help with a boring auth review

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

Mina Cruz

Be blunt about my plan for a boring auth review. 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, keep the patch smaller than the diagnosis.

Show all 3 messages

3402.9k

Idris Bello@idrisbello·3w ago

What I was getting wrong about reading a Postgres query plan

Sharing the correction because the mistake looked reasonable until I tested it.

Idris Bello

I want to learn reading a Postgres query plan, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain reading a Postgres query plan 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

6211.3k

Nico Lane@nicolane·4w ago

I needed a usable answer on a flaky test nobody can reproduce

This started as a messy question about a flaky test nobody can reproduce. The follow-up made the answer practical.

Nico Lane

I am stuck on a flaky test nobody can reproduce. I need to isolate a timing-dependent test failure and design a deterministic reproduction, but my current attempt is getting vague and too big. What would you check first?

Geminigemini-2.5-pro

First, shrink the decision. Do not solve the whole subject at once. 1. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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

3402.4k

Emil Novak@emilnovak·2w ago

Forked from@inesnavarro/The making practice sessions less repetitive tutor prompt I saved

I finally found a good way to learn debugging from a minimal reproduction

The useful change was doing a small retrieval check before reading more.

Emil Novak

I want to learn debugging from a minimal reproduction, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-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

631484

Silas Berg@silasberg·1mo ago

reading a Postgres query plan: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Silas Berg

I want to learn reading a Postgres query plan, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain reading a Postgres query plan 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

6313.7k

Soraya Aziz@sorayaaziz·1mo ago

debugging from a minimal reproduction: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Soraya Aziz

I want to learn debugging from a minimal reproduction, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

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

6314.2k

Rhea Haddad@rheahaddad·2w ago

I asked Gemini for a second opinion on a small CLI people can trust

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

Rhea Haddad

Be blunt about my plan for a small CLI people can trust. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Geminigemini-2.5-pro

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, keep the patch smaller than the diagnosis.

Show all 3 messages

340613

Nia Costa@niacosta·3w ago

Gemini found the hole in my reviewing agent-written code plan

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

Nia Costa

For reviewing agent-written code, 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 reviewing agent-written code, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3301.4k

Julian Scott@julianscott·3w ago

ChatGPT was overcomplicating queue retries, so I reset the question

This started as a messy question about queue retries. The follow-up made the answer practical.

Julian Scott

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

ChatGPTgpt-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, keep the patch smaller than the diagnosis.

Show all 3 messages

3301.3k

Eva Kovac@evakovac·2mo ago

The reading a Postgres query plan tutor prompt I saved

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

Eva Kovac

Tutor me on reading a Postgres query plan. 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 worked exampl

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain reading a Postgres query plan 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

6415.1k

Kenji Fujita@kenjifujita·2mo ago

I finally found a good way to learn using property-based tests

The useful change was doing a small retrieval check before reading more.

Kenji Fujita

I want to learn using property-based tests, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain using property-based tests 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

6214.6k

Ronan Byrne@ronanbyrne·4w ago

A practice-first plan for using property-based tests

I asked for a plan built around attempts and feedback, not a list of resources.

Ronan Byrne

I want to learn using property-based tests, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain using property-based tests 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

6312.3k

Zuri Mensah@zurimensah·4w ago

The finding duplicated state in React tutor prompt I saved

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

Zuri Mensah

Tutor me on finding duplicated state in React. 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 worked ex

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain finding duplicated state in React 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

6311.8k

Ben Brooks@benbrooks·1mo ago

I asked Gemini for a second opinion on React state that keeps drifting

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Ben Brooks

Be blunt about my plan for React state that keeps drifting. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Geminigemini-2.5-pro

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, keep the patch smaller than the diagnosis.

Show all 3 messages

3302.7k

Drew Bell@drewbell·4w ago

What finally made TypeScript types at an API boundary click for me

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Drew Bell

Help me replace hopeful casts with validation and useful failure messages. 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 recommendation. Otherwise, sta

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 TypeScript types at an API boundary, I would start with these checks: - Reproduce the failure before changing code - Keep the patch smaller than the diagnosis - Write the rollback before deployment If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3301.8k

Explore

Explore

Explore

The using property-based tests tutor prompt I saved

finding duplicated state in React: a study session that did not turn into more notes

React state that keeps drifting: the version with actual constraints

My notes from fixing a safe dependency upgrade

What I was getting wrong about reviewing code written by an agent

The cache invalidation without folklore prompt I actually kept

The checklist I use for Postgres query tuning

The designing idempotent background jobs tutor prompt I saved

The question that cleaned up database migration rehearsal

API error handling, minus the vague advice

A blunt review of my approach to a safe dependency upgrade

planning a zero-downtime migration: a study session that did not turn into more notes

The learning TypeScript at runtime boundaries tutor prompt I saved

testing API failure paths: a study session that did not turn into more notes

What I was getting wrong about debugging from a minimal reproduction

How I ask for help with a boring auth review

What I was getting wrong about reading a Postgres query plan

I needed a usable answer on a flaky test nobody can reproduce

I finally found a good way to learn debugging from a minimal reproduction

reading a Postgres query plan: a study session that did not turn into more notes

debugging from a minimal reproduction: a study session that did not turn into more notes

I asked Gemini for a second opinion on a small CLI people can trust

Gemini found the hole in my reviewing agent-written code plan

ChatGPT was overcomplicating queue retries, so I reset the question

The reading a Postgres query plan tutor prompt I saved

I finally found a good way to learn using property-based tests

A practice-first plan for using property-based tests

The finding duplicated state in React tutor prompt I saved

I asked Gemini for a second opinion on React state that keeps drifting

What finally made TypeScript types at an API boundary click for me