◆ Amazon DynamoDB

Modify software to correct errors

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCorrect the bug in the user profile update API that's causing the 'email already exists' error…+
Correct the bug in the user profile update API that's causing the 'email already exists' error for existing users. Deploy the fix to staging by Tuesday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we release the new user onboarding flow, there's a critical bug where new users…+
Before we release the new user onboarding flow, there's a critical bug where new users occasionally get stuck in a pending state. Investigate the database transaction logic for the user creation process, identify the race condition, and propose a robust fix that prevents data inconsistencies.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA critical bug is sporadically corrupting customer order data, but only on specific high-volume…+
A critical bug is sporadically corrupting customer order data, but only on specific high-volume days.
A critical bug is sporadically corrupting customer order data, but only on specific high-volume days, making it incredibly hard to reproduce. The sales team is furious, and we need a fix yesterday. I'm afraid to push a change without fully understanding the root cause. What's the most effective diagnostic approach for this intermittent data corruption, and what's the safest way to implement a fix without introducing new regressions?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently spend too much time debugging intermittent production issues that should have been…+
I frequently spend too much time debugging intermittent production issues that should have been caught earlier.
I frequently spend too much time debugging intermittent production issues that should have been caught earlier in development. This often involves complex database interactions. What habit should I change in my coding and testing practices to proactively identify and prevent these hard-to-reproduce, data-related bugs before they ever reach production?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.