◆ JavaScript

Optimize loop performance

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 taskA hot loop in the rendering path is causing frame drops; optimize the loop that builds the…+
A hot loop in the rendering path is causing frame drops; optimize the loop that builds the virtual list by removing unnecessary allocations, hoisting invariant calculations, and using indexed access rather than repeated property lookups. Ensure the change keeps identical output and cut per-iteration work so the 1000-item render drops from 120ms to under 40ms.
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 submit the loop change to reviewers, make the optimization clear and safe: show the…+
Before I submit the loop change to reviewers, make the optimization clear and safe: show the current per-iteration cost and the proposed lowered cost, surface which expressions were hoisted or memoized, highlight any changes that affect mutation order, and flag tests that should be added to guard against subtle state bugs. Recommend ways to measure the improvement in CI.
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 replaced a helper with a more expressive one and now the 500-item list render doubled in…+
A loop in list rendering just became the slow path
I replaced a helper with a more expressive one and now the 500-item list render doubled in time; the hot spot seems to be a loop that allocates objects each iteration. I cannot tell whether eliminating allocations or changing the loop form will help more. Which quick experiment will give the clearest signal and how should I measure it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI repeatedly ship code where naive loops cause regressions in medium-size datasets, and each…+
Repeated loop inefficiencies across features
I repeatedly ship code where naive loops cause regressions in medium-size datasets, and each fix takes an afternoon. Where am I most likely being sloppy — micro-allocation, property access, or algorithm choice — and what single coding habit change will prevent these loop problems in future reviews?
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.