◆ Amazon DynamoDB

Use 'IN' statement in FilterExpression

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 taskI need to fetch all orders for customers with IDs 'cust123', 'cust456', and 'cust789' from the…+
I need to fetch all orders for customers with IDs 'cust123', 'cust456', and 'cust789' from the 'orders' table. Get all attributes for these specific orders.
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 send this customer segment report to marketing, I need to make sure I'm only including…+
Before I send this customer segment report to marketing, I need to make sure I'm only including users from the 'premium' and 'enterprise' tiers. Fetch all users from the 'users' table who belong to these tiers, but only return their 'userId' and 'email' for the report.
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 analytics dashboard is showing inconsistent sales data for 'electronics', 'apparel', and…+
The analytics dashboard is showing inconsistent data for a specific set of product categories.
The analytics dashboard is showing inconsistent sales data for 'electronics', 'apparel', and 'homegoods'. I suspect our data pipeline might be misprocessing these categories. I can't tell if the raw 'sales' table data itself is wrong or if the aggregation logic is flawed. What's the best way to quickly check the 'category' attribute for these specific values in the 'sales' table to see if the raw data is as expected, and what's my next move if it's not?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly having to pull data for specific lists of IDs or categories, and it feels like…+
I frequently need to query data based on a list of specific values, and it's always a manual effort.
I'm constantly having to pull data for specific lists of IDs or categories, and it feels like I'm reinventing the wheel every time. I worry I'm missing a more efficient pattern to handle these 'list-based' lookups. What habit should I change to make these types of queries faster and less prone to manual error?
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.