◆ JavaScript

Write a function

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 a function that converts the CSV export from our analytics into the structure our API…+
I need a function that converts the CSV export from our analytics into the structure our API expects. Write a function named parseAnalyticsCsv that takes a CSV string and returns an array of objects with keys date (ISO), userId (string), and events (number). Include input validation and a thrown Error if required columns are missing. Keep it compatible with Node 18 and browsers.
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 merge this into the repo, make the function easy to review and maintain: surface the…+
Before I merge this into the repo, make the function easy to review and maintain: surface the assumptions about date formats and header names up front, make error messages actionable, and add a short example showing input CSV and resulting output. Flag any lines that would make a reviewer hesitate about edge cases like empty rows or quoted fields.
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 wrote parseAnalyticsCsv and most tests pass but CI fails when the CSV contains "01/02/2024"…+
I wrote parseAnalyticsCsv but tests fail on one case
I wrote parseAnalyticsCsv and most tests pass but CI fails when the CSV contains "01/02/2024" dates. I am not sure whether those are month/day or day/month in production. The code currently uses Date.parse. Who should I ask to decide the format, what questions do I ask them, and what is the safest interim code change so CI stops failing without changing production data interpretation?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver several projects I keep writing similar CSV parsing utilities that diverge on tiny…+
I keep rewriting parsing functions for slightly different CSVs
Over several projects I keep writing similar CSV parsing utilities that diverge on tiny assumptions — date formats, optional columns, trimming rules. Where am I losing time and introducing bugs, and what single pattern or library and three conventions should I adopt to avoid doing this again?
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.