◆ Amazon DynamoDB

Fix processes that resulted in 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
See the prompt↓All Amazon DynamoDB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFix the 'OrderProcessing' service to correctly handle duplicate order submissions, preventing…+
Fix the 'OrderProcessing' service to correctly handle duplicate order submissions, preventing the creation of multiple entries for the same buyer. Deploy the patch by end of day.
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 I push this fix for the 'OrderProcessing' service, make sure it's resilient. Consider…+
Before I push this fix for the 'OrderProcessing' service, make sure it's resilient. Consider what other edge cases could lead to data inconsistencies beyond just duplicate submissions, like incomplete payment notifications, and ensure the solution handles them gracefully to avoid future errors.
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 payment processing error just hit production, causing a buyer's transaction to fail,…+
A critical payment processing error just occurred, but the logs are unhelpful and I don't know where to start looking.
A critical payment processing error just hit production, causing a buyer's transaction to fail, and the logs are showing generic 'internal server error' messages without specific details. I'm afraid of a cascading failure if this isn't resolved quickly, but I can't pinpoint the exact service or database interaction that failed. The finance director is asking for an immediate update. What's the most effective way to quickly diagnose the root cause of this type of vague error in a distributed system, and what's the safest first step to take without causing more disruption?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe're constantly spending too much time on production error diagnosis because the initial logs…+
We frequently get vague production errors that are hard to trace, leading to long debugging cycles.
We're constantly spending too much time on production error diagnosis because the initial logs are often too vague to be useful. This pattern costs us credibility with the business and delays critical fixes. What habit should I change in how we design our error logging and monitoring to ensure we have actionable information from the start, making debugging faster and more precise?
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.