◆ JavaScript

Log values to console

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 debug why user objects look wrong. Insert console.log statements showing the user…+
I need to debug why user objects look wrong. Insert console.log statements showing the user variable shape before and after the transformation step, include labels and the component name, and remove them after I confirm the values. Keep logs succinct and avoid logging entire large objects — only show the fields that matter.
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 open a PR with debug logs, make the output reviewer-friendly. Move the two…+
Before I open a PR with debug logs, make the output reviewer-friendly. Move the two console.logs to a single labeled log with the component name, the user id, and the fields that changed. Explain in the PR why these fields were chosen and where to remove the log after verification.
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 put console.log(user) in three places but the devtools show huge objects and timestamps float…+
I added console.logs but the output is noisy and hard to read
I put console.log(user) in three places but the devtools show huge objects and timestamps float the output. I need to know the user id and the roles array only. What's the exact console statement I should use to show just those fields with a clear label so I can spot where roles change?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur repo accumulates stray console logs that slow debugging and leak data. I want a team habit…+
We leave debug logs in merged PRs and the console gets noisy
Our repo accumulates stray console logs that slow debugging and leak data. I want a team habit to keep logs useful. Propose one naming convention for temporary logs, one small lint rule or CI check to flag leftover console.log, and a short reviewer checklist item to catch them.
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.