◆ JavaScript

Map array to values

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 product objects and need an array of just their prices to feed into a chart.…+
I have an array of product objects and need an array of just their prices to feed into a chart. Produce code that maps the products array to an array of numeric prices, converting strings to numbers and falling back to 0 for missing price fields. Keep it a one-liner I can drop into renderChart.
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 hand the mapping to design, make it obvious where prices come from. Put the prices…+
Before I hand the mapping to design, make it obvious where prices come from. Put the prices array at the top of the snippet, show the string-to-number conversion and the fallback, and flag any products missing a price so reviewers can ask the API team. Keep comments minimal and the transformation readable.
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 mapped product.price directly and the chart displayed NaN for some entries. The product…+
Chart showed NaN values after mapping
I mapped product.price directly and the chart displayed NaN for some entries. The product owner, Maria, will complain the numbers don’t add up. I don’t know whether the API sometimes sends empty strings, null, or malformed values. What’s the likely root cause and the fastest fix for the mapping so the chart remains stable?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several front-end pages we repeatedly map objects to values without consistent parsing,…+
Mapping inconsistently across components
Across several front-end pages we repeatedly map objects to values without consistent parsing, leading to NaN, undefined, and display bugs. It costs time tracking down where a bad value slipped in. Which habit should we change to stop this: centralise parsing at the API boundary, always map with a sanitizer util, or add type checks? Recommend one change and how to roll it out with minimal churn.
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.