◆ JavaScript

Iterate over object properties

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 taskLoop through each property in the 'userProfile' object and log its key and value to the console…+
Loop through each property in the 'userProfile' object and log its key and value to the console for debugging.
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 logging 'userProfile' properties, ensure we only display non-sensitive data like…+
Before logging 'userProfile' properties, ensure we only display non-sensitive data like 'username' and 'email', skipping 'passwordHash' and 'authToken' to avoid exposing credentials in the console during development.
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'm trying to iterate through the 'settings' object to display all user preferences on the…+
I'm trying to display all user preferences from the 'settings' object, but some are showing up as 'undefined' and others are just not appearing at all.
I'm trying to iterate through the 'settings' object to display all user preferences on the profile page, but some values are coming up as 'undefined' and others are simply not showing up. I'm afraid I'm missing some properties or misinterpreting their types, which could lead to a broken UI for users. What's the best way to reliably iterate and display all defined properties, handling potential nulls or empty strings gracefully?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often waste time debugging when iterating over objects because I accidentally include…+
I consistently struggle with iterating over objects, especially when dealing with inherited properties or non-enumerable ones.
I often waste time debugging when iterating over objects because I accidentally include inherited properties or miss non-enumerable ones, leading to incomplete or incorrect data displays. This impacts the accuracy of our reports. What habit should I change to make my object iteration always precise and include only the properties I intend, avoiding these common pitfalls?
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.