◆ Amazon DynamoDB

Perform website tests

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 taskRun the full suite of integration tests on the new user registration flow and report any…+
Run the full suite of integration tests on the new user registration flow and report any failures to the team channel by EOD Friday. Make sure the database connection pool is optimized for peak load during the tests.
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 push the new user profile update to staging, run the full test suite. Focus on how it…+
Before we push the new user profile update to staging, run the full test suite. Focus on how it handles concurrent writes to the user table, and flag any performance bottlenecks or data inconsistencies that could impact user experience.
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 new payment gateway integration tests are failing intermittently with timeouts, but only…+
The last test run for the new payment gateway integration showed intermittent timeouts, but only under specific load conditions.
The new payment gateway integration tests are failing intermittently with timeouts, but only when we simulate high concurrent transactions. We're getting pressure from the product owner to deploy by end of week. I'm worried we'll push a flaky system. What's the most likely cause for these intermittent timeouts, and what's the fastest way to diagnose and stabilize it without delaying the release?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep finding critical bugs late in the development cycle, usually during final integration…+
I keep finding critical bugs late in the development cycle during final integration tests.
I keep finding critical bugs late in the development cycle, usually during final integration tests just before deployment. This causes last-minute scrambling and missed deadlines. What habit should I change to catch these issues earlier in the dev process, especially those related to database interactions and edge cases?
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.