◆ Amazon DynamoDB

Order results with query or scan

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 taskGet all recent orders from the 'Orders' table that were placed in the last 24 hours, and list…+
Get all recent orders from the 'Orders' table that were placed in the last 24 hours, and list them with the newest orders first for the operations dashboard.
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 display the recent orders on the operations dashboard, I need to ensure they are…+
Before I display the recent orders on the operations dashboard, I need to ensure they are sorted correctly and only show relevant details. Order them by 'order_timestamp' in descending order, and only include 'order_id', 'customer_id', and 'total_amount'.
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 operations team needs a list of the 100 most recent orders, sorted from newest to oldest.…+
The operations team needs recent orders sorted by time, but I'm not sure if I should use a query or a scan for this, given the table size.
The operations team needs a list of the 100 most recent orders, sorted from newest to oldest. I'm afraid of using a scan on the 'Orders' table because it's huge, but I'm not sure if a query can achieve the correct sorting efficiently without a specific index. What's the best way to get these sorted results without over-provisioning read capacity or 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 often need to retrieve data from tables and present it in a specific sorted order, but I…+
I keep running into issues with sorting results from tables, either by using inefficient scans or missing the right index strategy.
I often need to retrieve data from tables and present it in a specific sorted order, but I frequently struggle with choosing between scans and queries, leading to either slow operations or excessive read capacity usage. This impacts dashboard performance and my time. What habit should I change to consistently implement efficient sorting for data retrieval?
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.