◆ JavaScript

Test for an empty object

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 taskTest if the 'userPreferences' object I just received from the API is empty before trying to…+
Test if the 'userPreferences' object I just received from the API is empty before trying to display anything.
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 try to render the user's dashboard widgets, check if the 'widgetData' object is empty…+
Before I try to render the user's dashboard widgets, check if the 'widgetData' object is empty or contains no meaningful data, and if so, display a friendly 'no data available' message instead of a blank screen.
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 new analytics dashboard is occasionally showing a blank screen for certain users, and I…+
The new analytics dashboard is sometimes showing a blank screen for users, even when there should be data.
The new analytics dashboard is occasionally showing a blank screen for certain users, and I suspect the data object coming from the backend might be empty or malformed. We promised the sales team this would be live by Monday, and I'm afraid of rolling out a broken feature. Should I add a quick check for an empty object and display a generic message, or is it more critical to investigate why the backend is sending empty data in the first place, risking 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 patternI keep running into UI errors or broken components because data objects I expect to contain…+
I frequently encounter situations where data objects from APIs or user input are unexpectedly empty, leading to UI errors.
I keep running into UI errors or broken components because data objects I expect to contain information are sometimes empty, either from the API or user input. This leads to crashes or poor user experiences. What habit should I change to consistently validate incoming data for emptiness at the earliest possible point, so I stop debugging these preventable display issues?
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.