◆ Amazon DynamoDB

Evaluate feasibility of software projects

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 taskEstimate the development time for integrating the new payment gateway. Include time for API…+
Estimate the development time for integrating the new payment gateway. Include time for API integration, testing, and deployment to staging. Assume a standard three-person team for two weeks.
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 commit to using a serverless architecture for the new analytics dashboard, evaluate…+
Before I commit to using a serverless architecture for the new analytics dashboard, evaluate its long-term operational cost compared to our current EC2-based solution. Consider scaling costs, monitoring overhead, and potential vendor lock-in risks. I need to present a clear cost-benefit analysis to Maria by end of day Tuesday.
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 sales team just dropped a request for a real-time inventory lookup feature, demanding it by…+
The sales team wants a new real-time inventory lookup feature by the end of the quarter, but engineering is already at capacity with the Q3 roadmap.
The sales team just dropped a request for a real-time inventory lookup feature, demanding it by the end of the quarter to close a major deal. Our Q3 roadmap is already packed, and adding this means pushing something critical. I'm worried if we say no, we lose the deal, but saying yes means burning out the team and likely delivering a rushed, buggy solution. What's the best way to quickly assess the true impact of this new request on our existing commitments, and how should I frame the conversation with David, our head of sales, to manage expectations without jeopardizing the deal or team morale?
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 underestimating the time required for testing and bug fixing in our project plans,…+
I consistently underestimate the time needed for testing and bug fixing in our project estimates.
I keep underestimating the time required for testing and bug fixing in our project plans, leading to missed deadlines and rushed releases. It feels like I always focus on the 'happy path' development. What habit should I change in my project planning process to more realistically account for the inevitable complexities and rework, ensuring our estimates are more accurate and less stressful for the team?
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.