◆ Amazon DynamoDB

Develop web-accessible software

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 taskDeploy the new API gateway and Lambda functions for the user profile service to the staging…+
Deploy the new API gateway and Lambda functions for the user profile service to the staging environment by 3 PM today. Ensure the DynamoDB table permissions are correctly configured for read and write access from the Lambda functions.
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 deploying the user profile service to production, make sure it can handle a sudden spike…+
Before deploying the user profile service to production, make sure it can handle a sudden spike in traffic. Set up auto-scaling for the Lambda functions and provisioned concurrency for the DynamoDB table to prevent cold starts and throttling errors, especially during peak login times.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new user profile service went live an hour ago, and we're getting 'profile not found'…+
The new user profile service is live, but users are reporting 'profile not found' errors intermittently, even for existing accounts.
The new user profile service went live an hour ago, and we're getting 'profile not found' errors for existing users, but not consistently. The logs show successful writes, but reads are failing sometimes. I'm afraid we missed an eventual consistency edge case or a misconfigured index. What's the most likely cause, and how should I start debugging this without impacting other services?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting caught off guard by unexpected read/write capacity limits when new features…+
I keep getting caught off guard by unexpected read/write capacity limits when new features launch.
I keep getting caught off guard by unexpected read/write capacity limits when new features launch, leading to frantic scaling adjustments. This always happens when we underestimate initial user adoption or a specific feature's data access pattern. How can I change my habit to better anticipate and provision NoSQL database capacity for new services, avoiding reactive firefighting?
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.