◆ JavaScript

Generate random number in range

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 taskGenerate a random number between 1 and 100 for the daily lottery draw, so we have a fair…+
Generate a random number between 1 and 100 for the daily lottery draw, so we have a fair winner.
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 assigning a new user ID, generate a random 8-digit number, and then check if that ID is…+
Before assigning a new user ID, generate a random 8-digit number, and then check if that ID is already in use in our database, because we need unique IDs and can't risk collisions.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur 'generate secure password' feature is supposed to create strong passwords, but users are…+
The 'random password generator' is creating too many easily guessable passwords.
Our 'generate secure password' feature is supposed to create strong passwords, but users are complaining they're too simple, like 'password123'. I'm afraid the range or character set isn't broad enough. The security team is on my back. How can I ensure the generated passwords are truly random and meet our complexity requirements without making them impossible to type?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently need to generate random numbers for various features: user IDs, game outcomes,…+
I keep needing to generate random data, but the ranges or types are always slightly different.
I frequently need to generate random numbers for various features: user IDs, game outcomes, test data. Each time, the range, whether it's inclusive or exclusive, and whether it's an integer or float, changes slightly. This leads to me re-implementing similar logic and sometimes getting off-by-one errors. What habit should I change to make generating correctly-ranged random numbers more consistent and less error-prone?
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.