◆ JavaScript

Perform bulk updates

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 taskUpdate the 'status' field to 'Archived' for all customer records older than five years in the…+
Update the 'status' field to 'Archived' for all customer records older than five years in the main database.
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 perform this bulk update on all active user accounts, make sure the changes are…+
Before I perform this bulk update on all active user accounts, make sure the changes are reversible and that the update process won't lock up the database or impact live user sessions, flagging any potential data integrity risks.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA recent bulk update to user profiles inadvertently set the 'active' flag to 'false' for 20% of…+
A recent bulk update to user profiles inadvertently set the 'active' flag to 'false' for 20% of our paying customers.
A recent bulk update to user profiles inadvertently set the 'active' flag to 'false' for 20% of our paying customers. I'm afraid of massive customer churn and revenue loss, but I don't have a recent backup that isolates just those affected users. The customer support team is overwhelmed with calls. I can't tell if the script had a faulty filter or if the data source was corrupted. What's the likely diagnosis and the best next move to quickly revert the incorrect changes without affecting other data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time we do a bulk update, there's a significant risk of data corruption or unintended…+
Every time we do a bulk update, there's a significant risk of data corruption or unintended side effects.
Every time we do a bulk update, there's a significant risk of data corruption or unintended side effects. This often leads to frantic rollbacks and lost productivity. What habit should I change to minimize the risk of errors during bulk operations and ensure data integrity, making these updates less stressful and more reliable?
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.