◆ JavaScript

Iterate over arrays

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
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI have an array of user IDs and need to run an async check for each ID to refresh their cache.…+
I have an array of user IDs and need to run an async check for each ID to refresh their cache. Iterate the array so each ID is processed and any errors are collected; do not block the event loop unnecessarily. Provide the pattern I can drop into my refreshUsers function that returns when all checks finish and includes per-ID success or error.
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 use this iteration in the nightly job, make the approach obvious to the ops reviewer:…+
Before I use this iteration in the nightly job, make the approach obvious to the ops reviewer: show how to process IDs concurrently but with a maximum of five simultaneous requests, ensure errors for one ID don’t stop the rest, and return a summary of successes and failures. Keep the example concise and explain the concurrency choice in one sentence.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI implemented a forEach over user IDs and added await inside its callback; the refresh never…+
I started using forEach with await and tasks stalled
I implemented a forEach over user IDs and added await inside its callback; the refresh never completed. The job owner Jack will lose trust if the nightly run keeps hanging. I don’t know whether to switch to for...of, Promise.all, or a concurrency limiter. What caused the hang and what is the best fix that preserves concurrency control?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternRepeatedly on projects we write array.forEach with await or use Promise.all for thousands of…+
Iteration mistakes causing slow or broken jobs
Repeatedly on projects we write array.forEach with await or use Promise.all for thousands of items and blow memory or rate limits. It wastes hours in production incidents and postmortems. What single habit or small rule change will remove these errors: always use for...of with await, always limit concurrency, or prefer streaming APIs? Explain how to enforce it in code reviews and CI linters.
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.