◆ JavaScript

Address relationships using numbers and symbols

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 taskWrite a function that takes two numbers, 'a' and 'b', and returns their…+
Write a function that takes two numbers, 'a' and 'b', and returns their sum.
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 integrate this into the financial reporting module, enhance the calculation function.…+
Before I integrate this into the financial reporting module, enhance the calculation function. It should accept an array of numbers, calculate their sum, average, and standard deviation, and handle non-numeric inputs by returning an error message.
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 financial calculation function I wrote is returning 'NaN' for the quarterly revenue report,…+
The financial calculation function is returning 'NaN' for a critical report.
The financial calculation function I wrote is returning 'NaN' for the quarterly revenue report, which is due to the CEO by end of day. I'm afraid this could delay the report and make the finance team look bad, and I can't tell the project manager I don't know why it's failing. I've checked for nulls and undefined, but the input array looks clean. Is this likely a data type coercion issue, a floating-point precision error, or something more fundamental in my standard deviation calculation? What's the quickest way to diagnose and fix this before the deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy numerical functions frequently fail silently or produce obscure errors when encountering…+
My numerical functions often fail silently or with obscure errors on edge cases.
My numerical functions frequently fail silently or produce obscure errors when encountering edge cases or unexpected input formats, leading to unreliable data processing. This erodes confidence in our data. What habit should I change in how I design and test these functions to ensure they are robust, handle all valid inputs, and provide clear, informative errors for invalid ones?
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.