◆ JavaScript

Search databases

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 taskQuery the user database for all active accounts created after January 1, 2023, and return their…+
Query the user database for all active accounts created after January 1, 2023, and return their email addresses and last login dates by Friday.
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 run this database query, optimize it for speed and resource usage. We've seen…+
Before I run this database query, optimize it for speed and resource usage. We've seen performance issues on large datasets, so ensure it handles millions of records efficiently and doesn't lock up the main server during peak hours.
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 analytics dashboard is showing wildly inconsistent numbers compared to the old one, and…+
The new analytics dashboard is showing wildly inconsistent numbers compared to the old one.
The new analytics dashboard is showing wildly inconsistent numbers compared to the old one, and I'm getting heat from the product manager, Sarah, who needs accurate data for her presentation to the board on Monday. I suspect a data source or join issue, but I can't pinpoint it without disrupting the live system. What's the fastest way to diagnose this without causing downtime or further data corruption?
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 losing hours debugging subtle, hard-to-reproduce errors in our API integrations,…+
I keep losing hours debugging subtle, hard-to-reproduce errors in our API integrations.
I keep losing hours debugging subtle, hard-to-reproduce errors in our API integrations, especially with third-party services that change without notice. This impacts release schedules and my credibility with the project lead. What habit should I change to anticipate these integration failures better and reduce my debugging time?
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 JavaScript'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.