Log values to console — AI Prompts for JavaScript

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

I 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.

Improve — make it easier to accept

Before I open a PR with debug logs, make the output reviewer-friendly. Move the two console.logs to…

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.

Decide — diagnose the stuck moment

I put console.log(user) in three places but the devtools show huge objects and timestamps float the…

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?

Become — change the pattern

Our repo accumulates stray console logs that slow debugging and leak data. I want a team habit to…

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.

Next to this one

Other programming language work people do in JavaScript.

Handle HTTP response Handle promise result Implement accessibility features Import a module Iterate over arrays Manage authentication flow Manage component state Manage cookies Manipulate DOM elements Map array to values

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt