Mateo Chen (@mateochen)

Forked from@idrisbello/What I was getting wrong about designing idempotent background jobs

What I was getting wrong about designing idempotent background jobs

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

Mateo Chen

I want to learn designing idempotent background jobs, 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 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

6100

Mateo Chen@mateochen·3w ago

I asked Gemini for a second opinion on structured output that stays readable

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

Mateo Chen

Be blunt about my plan for structured output that stays readable. 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, mark missing evidence instead of filling it in.

Show all 3 messages

332138

Mateo Chen@mateochen·2mo ago

The structured output that stays readable prompt I actually kept

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

Mateo Chen

Help me return valid JSON while keeping the substance useful to a human reviewer. 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. Otherwi

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 structured output that stays readable, 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

3314k

Mateo Chen@mateochen·2mo ago

A smaller way to tackle structured output that stays readable

A compact prompt and the response it produced. Replace the bracketed parts with your own details.

Mateo Chen

For structured output that stays readable, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

ChatGPTgpt-5

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 structured output that stays readable, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3413k

Mateo Chen@mateochen·3mo ago

The checklist I use for structured output that stays readable

This started as a messy question about structured output that stays readable. The follow-up made the answer practical.

Mateo Chen

I am stuck on structured output that stays readable. I need to return valid JSON while keeping the substance useful to a human reviewer, 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. 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

3411.5k

Mateo Chen@mateochen·3mo ago

structured output that stays readable: the version with actual constraints

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

Mateo Chen

Give me a short checklist for structured output that stays readable. 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 - [ ] 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

3314.2k

Public pits

What I was getting wrong about designing idempotent background jobs

I asked Gemini for a second opinion on structured output that stays readable

The structured output that stays readable prompt I actually kept

A smaller way to tackle structured output that stays readable

The checklist I use for structured output that stays readable

structured output that stays readable: the version with actual constraints