◆ JavaScript

Generate random value

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 taskI need a random token for a password-reset link for user 16742. Generate a cryptographically…+
I need a random token for a password-reset link for user 16742. Generate a cryptographically secure random string of 32 URL-safe characters, base64-url encoded, and attach it to resetTokens with an expiry 15 minutes from now. Return the token so I can send it in the email.
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 put random tokens into production, make the generation easy to audit: show the entropy…+
Before I put random tokens into production, make the generation easy to audit: show the entropy bits, write a one-line comment explaining why the method is cryptographically secure, and flag any uses of Math.random or non-cryptographic APIs. Also provide a deterministic fallback for tests that can be toggled without changing the production path.
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 just generated a password-reset token for user 16742 and a support case says the token…+
I issued a reset token and a user reported they received the same token twice.
I just generated a password-reset token for user 16742 and a support case says the token matched another recent token. I suspect a non-cryptographic PRNG slipped into the code path, or I accidentally seeded a deterministic routine for tests. I can’t tell whether the bug is in token creation, storage, or a test harness. What is the most likely cause and the immediate code checks I should run to confirm and fix it now?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver time I see intermittent token collisions or predictable tokens in logs and it costs hours…+
Tokens occasionally collide in logs
Over time I see intermittent token collisions or predictable tokens in logs and it costs hours in incident triage. I keep using ad-hoc token helpers that are convenient for dev but unsafe for prod. What practice and minimal tooling change will stop these incidents, and how should I handle testability without weakening security in production?
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.