◆ JavaScript

Upload files asynchronously

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 taskGet the new user profile images from the upload form to the server without freezing the…+
Get the new user profile images from the upload form to the server without freezing the browser, then update the UI once they're all done.
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 we push the new image upload feature live, make sure that if a user drops five large…+
Before we push the new image upload feature live, make sure that if a user drops five large files, the page stays responsive and they get clear feedback on each file's progress, not just a spinner at the end.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers in rural areas are complaining about image uploads timing out, but it works fine on my…+
The new image upload is failing intermittently for users with slow connections, but I can't reproduce it locally.
Users in rural areas are complaining about image uploads timing out, but it works fine on my fast connection. I'm worried we're retrying too aggressively or not handling partial uploads correctly, and the product lead is pressing for a fix by Friday. What's the most likely cause of this intermittent failure, and what's the quickest way to diagnose it without deploying a full logging solution?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly debugging file upload issues that are hard to reproduce outside of specific…+
I keep getting pulled into debugging file upload issues that are hard to replicate.
I'm constantly debugging file upload issues that are hard to reproduce outside of specific network conditions or user environments. This is costing us a lot of time and user trust. What habit should I change in how I design or test file upload mechanisms to catch these edge cases earlier and prevent them from reaching production?
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.