◆ JavaScript

Set default function parameter 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
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 taskModify the `createUser` function so that if no role is specified, it defaults to 'member',…+
Modify the `createUser` function so that if no role is specified, it defaults to 'member', otherwise use the provided role.
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 we merge the user management module, ensure that the `assignPermissions` function always…+
Before we merge the user management module, ensure that the `assignPermissions` function always has a fallback role if none is explicitly passed, so we don't accidentally create users with no access, which has caused support tickets before.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new developer just committed code that's breaking user creation because they're not…+
A new developer just pushed code that broke user creation because they forgot to pass a required role.
A new developer just committed code that's breaking user creation because they're not explicitly passing a user role, and it's throwing an error. I'm afraid this will happen again as new people join. The project manager wants to know why the system isn't more robust. Should I enforce a default at the function signature level, or is there a more idiomatic way to handle this defensively without making the code too rigid?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly adding boilerplate code to check if function parameters are defined and…+
I frequently find myself adding null checks or default assignments for function parameters.
I'm constantly adding boilerplate code to check if function parameters are defined and assigning defaults, especially for optional configuration objects or user roles. This feels repetitive and prone to oversight. What habit should I change in how I define function interfaces or handle optional arguments to reduce this manual overhead and make the code more resilient to missing inputs?
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.