◆ JavaScript

Compare values safely

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 need to check whether user input equals a stored config value without misclassifying 0, '',…+
I need to check whether user input equals a stored config value without misclassifying 0, '', null or NaN. Compare the two values so the result is true only when they are the same value and same type, not just loosely equal. If the values are objects or arrays, treat them as unequal unless they reference the exact same object. Use concise code I can paste into a validation function used on form submit.
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 add this comparison into the login flow, make the outcome easy for reviewers to see.…+
Before I add this comparison into the login flow, make the outcome easy for reviewers to see. Put the strict equality result at the top of the snippet, comment why === is chosen over ==, and flag the cases that commonly confuse reviewers: 0 versus '0', null versus undefined, NaN behaviour. Make the code two or three lines max and readable for a junior dev.
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 used == to compare an input value and a stored preference and it returned true when the…+
I compared values and got unexpected true from a loose check
I just used == to compare an input value and a stored preference and it returned true when the input was an empty string and the preference was 0. Priya on QA will call this a bug because empty string isn’t a valid numeric choice. I’m unsure whether to change all comparisons to === or adjust upstream parsing. What’s the likely cause and the safest next step for production code?
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 projects we keep patching bugs where == accepts unintended inputs: form fields,…+
Loose equality causes subtle bugs across code reviews
Across several projects we keep patching bugs where == accepts unintended inputs: form fields, query params, feature flags. It eats review time and surfaces in production as wrong behaviour. Which habit change will stop this recurring issue: always coerce inputs first, always use strict equality, add a lint rule, or a combination? Recommend the single best practice and how to make it stick in our team.
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.