◆ Amazon DynamoDB

Add a column in 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
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 taskAdd a new 'shipping_address' attribute to the 'orders' table for order 'ORD-001'. The value…+
Add a new 'shipping_address' attribute to the 'orders' table for order 'ORD-001'. The value should be '123 Main St, Anytown, USA'.
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 we launch the new user profile page, add a 'profile_picture_url' column to the 'users'…+
Before we launch the new user profile page, add a 'profile_picture_url' column to the 'users' table. Make sure it's a string and defaults to an empty string if not provided, so the frontend doesn't break.
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 need to add a 'last_updated_by' attribute to the 'documents' table to track who made the…+
We need to add a 'last_updated_by' column to the 'documents' table, but I'm unsure about the impact on existing items.
We need to add a 'last_updated_by' attribute to the 'documents' table to track who made the last change. My concern is how this affects the 50 million existing documents that won't have this field. Should I backfill it with a null, or is there a way to add it so the application safely handles its absence for older items without errors?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently get caught off guard when new features require adding attributes to existing…+
I often find myself scrambling to add new attributes to tables without a clear strategy for existing data.
I frequently get caught off guard when new features require adding attributes to existing tables. This often leads to hasty backfills or application errors on older records. What habit can I change to proactively plan for schema evolution, ensuring new attributes are added smoothly and existing data is handled gracefully, avoiding production fires?
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.