◆ Amazon DynamoDB

Document technical factors

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 taskGenerate a markdown document detailing the schema for the 'products' DynamoDB table, including…+
Generate a markdown document detailing the schema for the 'products' DynamoDB table, including primary key, all attributes, their data types, and any Global Secondary Indices with their respective keys and projected attributes.
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 hand off this service to the operations team, improve the documentation for the NoSQL…+
Before we hand off this service to the operations team, improve the documentation for the NoSQL database integration. They need to understand the data model, common access patterns, and potential failure modes without having to dig through code. Focus on clarity, completeness, and highlighting operational considerations, so they can effectively support it.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentDuring an incident, the on-call engineer couldn't quickly understand the NoSQL database data…+
During an incident, the on-call engineer couldn't quickly understand the DynamoDB data model.
During an incident, the on-call engineer couldn't quickly understand the NoSQL database data model for the impacted service, delaying resolution. I'm afraid our documentation is either outdated or too sparse, and he couldn't find the critical information about item structure or access patterns. I can't tell if it's a discoverability issue or a content gap. What's the immediate next step to get him the info he needs and what's the best way to prevent this going forward?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur NoSQL database documentation is consistently out of sync with the actual schema and usage,…+
Our DynamoDB documentation is consistently out of sync with the actual schema and usage.
Our NoSQL database documentation is consistently out of sync with the actual schema and usage, leading to confusion and errors for new team members and during incidents. It feels like we treat documentation as an afterthought. What habit should we change to ensure our technical factors for the NoSQL database are always accurately documented and easily accessible, making onboarding smoother and incident response faster?
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.