◆ Amazon DynamoDB

Select programming languages or design tools

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 taskSelect Python for the new data processing script. It needs to integrate with our existing data…+
Select Python for the new data processing script. It needs to integrate with our existing data lake and run on a scheduled basis. Use the standard libraries for CSV parsing and database interaction.
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 start developing the new mobile application, evaluate whether to use React Native or…+
Before we start developing the new mobile application, evaluate whether to use React Native or native iOS/Android development. Consider our current team's skill set, the required performance characteristics for the user interface, and the long-term maintenance implications. I need a clear recommendation for Sarah, our product manager, by Friday.
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 team is completely split on whether to use Angular or Vue for the new customer portal. Half…+
We need to choose a new frontend framework for our customer portal, but the team is split between Angular and Vue, and I'm not sure which factors are most important right now.
The team is completely split on whether to use Angular or Vue for the new customer portal. Half the developers are pushing for Angular because of its maturity and strict structure, while the other half prefers Vue for its flexibility and faster development cycle. I'm worried about making the wrong choice and either alienating half the team or picking something that won't scale with our future needs. What are the key technical and organizational factors I should prioritize in this decision, and what's the best way to facilitate a consensus without just dictating a choice?
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 pattern where I often lean towards adopting the latest programming language or…+
I often find myself making technology choices based on what's 'new and shiny' rather than what's truly best for the project.
I've noticed a pattern where I often lean towards adopting the latest programming language or design tool, sometimes at the expense of stability or team expertise. It feels like I'm chasing trends instead of optimizing for long-term project health. What habit should I change to ensure my technology selection process is more grounded in practical project requirements, team capabilities, and maintainability, rather than just the excitement of a new tool?
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.