Your daily AI tutor

Get smarter, one question a day.

Explain an idea in your own words. Your tutor finds the gaps and helps you work through them.

Free to try. No account or card needed.

People using Unlearnt work at

DoorDashDeliverooAnthropicMetaGoogleSpotifyFigmaStripe

The experience

See what happens when you think out loud.

No lectures. Unlearnt asks the next question that makes you reconsider your answer.

See Unlearnt in action

Today's question

A payment request times out. Is retrying with an idempotency key enough to guarantee no double charge?

You

I'd say yes. The server checks the key before charging, so the second request just gets ignored.

Unlearnt

What if two requests with that key hit different workers at the same moment, before either records it?

You

Oh. Both workers could see that the key doesn't exist and both try to charge. I hadn't thought about the timing.

Unlearnt

What would have to change to stop both workers from claiming that key?

You

Only one should be able to claim it, maybe through a unique database insert. But if the first is still processing, I'm not sure what the retry should return.

01Your Understanding Map

Find the gap you didn't see.

Your explanation becomes a clear picture of what you understood, what needs work and where to go next.

What Unlearnt noticed

You assumed checking an idempotency key makes retries safe. But two workers can both pass that check before either writes the key. You spotted the race only after considering concurrency.

From your explanation

Understood

You identified how a check-then-charge race can produce two effects and suggested a unique claim so only one worker proceeds.

Strengthen

You haven't resolved what the second worker should return while the first payment is still processing, or how to replay the outcome safely.

Explore next

What if the payment succeeds but the worker crashes before recording its result?

Try a question like this

02Learning that sticks

Come back to it. See it differently.

Difficult ideas return from a new angle. Each question builds on the thinking you've already done.

Today

Two payment retries arrive simultaneously. Can an idempotency-key lookup alone prevent double charges?

Later · A new angle

Your payment provider charged the card, but your server crashed before saving the outcome. How should a retry behave?

The connection

A key identifies a retry, but the claim, side effect and recorded result still need coordination.

03Over time

Get to know how you think.

Your Learning Profile connects patterns across your explanations, with evidence and a useful next step.

Your Learning Profile

Pattern noticed

You tend to trust a solution on the happy path before testing what happens when requests overlap.

What revealed it

With payment retries, you assumed checking an idempotency key was enough. In a separate stock-update example, you also assumed two buyers wouldn't change inventory at once.

Try next

When something looks safe, ask: what could two people or systems do at the same instant?

The thinking behind Unlearnt

Less collecting.
More understanding.

Perspectives on curiosity and active learning.

Beyond the app

It matters most when you're not in the app.

What you learn should go somewhere. Into your next meeting, a decision, or a problem you can finally work through.

Ideas worth understanding

Start with a question.

See how our AI tutor works