◆ Amazon DynamoDB

Build web applications using DynamoDB

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 taskBuild a new DynamoDB table for the user profiles, ensuring it's ready to handle 10,000 requests…+
Build a new DynamoDB table for the user profiles, ensuring it's ready to handle 10,000 requests per second for reads and writes, and set up auto-scaling for both. I need it by EOD Friday for the beta launch.
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 launch the new user profile table, make sure it's optimized for our expected traffic…+
Before I launch the new user profile table, make sure it's optimized for our expected traffic spikes. I need to avoid throttling during peak login times, so review the provisioned capacity and auto-scaling settings to prevent any user-facing 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 momentThe new user profile table for the beta is hitting high latency spikes during load testing,…+
The new DynamoDB table is showing high latency spikes during load testing.
The new user profile table for the beta is hitting high latency spikes during load testing, even though I scaled up the read and write capacity. Mark from product is breathing down my neck about the Friday launch. I can't tell if it's an issue with the partition key distribution or if the application is just hammering it too hard. What's the likely bottleneck, and what's the fastest way to stabilize performance before tomorrow?
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 struggling to correctly estimate initial capacity for new DynamoDB tables, leading to…+
I keep over-provisioning or under-provisioning new DynamoDB tables.
I keep struggling to correctly estimate initial capacity for new DynamoDB tables, leading to either wasted spend or performance issues right out of the gate. This cycle is burning too much time in pre-launch tuning. What habit should I change in my planning to get closer to optimal capacity on the first try, considering our unpredictable user growth?
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.