◆ Amazon DynamoDB

Program all kinds of software systems

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 taskWrite a Python script that reads customer data from 'customers.csv', filters for active…+
Write a Python script that reads customer data from 'customers.csv', filters for active customers, and inserts their 'id' and 'email' into the 'ActiveUsers' table. Ensure the script handles malformed CSV rows gracefully and logs any errors.
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 finalize the design for the new authentication service, make sure it's resilient to…+
Before I finalize the design for the new authentication service, make sure it's resilient to common attack vectors like brute-force and SQL injection. Design the API endpoints to use proper input validation and rate limiting, and ensure sensitive data like passwords are encrypted at rest and in transit. I need to present this to the security team for review next week.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe just pushed the new analytics module to production, and the numbers it's generating are…+
We've deployed the new analytics module, but the data it's reporting is inconsistent with our existing reports, and I can't find the discrepancy.
We just pushed the new analytics module to production, and the numbers it's generating are significantly different from our old reporting system. I've checked the data sources, the transformation logic, and the aggregation queries multiple times, but I can't pinpoint where the discrepancy is coming from. Our CEO, Mark, is asking for a definitive answer by end of day. I'm afraid of reporting incorrect data to leadership. Is there a systematic approach to debugging data discrepancies like this, especially when the logic is complex, and what's the best way to communicate this uncertainty to Mark without losing credibility?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI've noticed a recurring problem where I often have to go back and refactor significant…+
I frequently find myself having to refactor code because I didn't adequately consider future scaling or maintenance needs during the initial design.
I've noticed a recurring problem where I often have to go back and refactor significant portions of code shortly after deployment because I didn't fully account for scaling, performance, or future maintenance requirements during the initial design phase. It feels like I'm always building for 'today's' problem, not 'tomorrow's'. What habit should I change in my software design process to consistently build more robust, forward-looking systems that minimize costly rework down the line?
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.