◆ JavaScript

Design mathematical data models

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 taskDevelop a mathematical model to predict the spread of a new viral strain based on R0=2.5, a…+
Develop a mathematical model to predict the spread of a new viral strain based on R0=2.5, a 3-day incubation period, and a 7-day infectious period, assuming a closed population of 10,000.
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 present this epidemiological model to Dr. Lee's team, make it easily interpretable for…+
Before I present this epidemiological model to Dr. Lee's team, make it easily interpretable for public health officials – clearly articulate the model's assumptions, visualize the impact of varying intervention strategies like 50% vaccination, and highlight the confidence intervals around key predictions.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy mathematical model for predicting supply chain disruptions is consistently underestimating…+
My predictive model for supply chain disruptions is consistently underestimating the impact of minor delays.
My mathematical model for predicting supply chain disruptions is consistently underestimating the impact of even minor delays, leading to inaccurate inventory forecasts and unexpected stockouts. The logistics manager is frustrated, and I'm afraid my initial assumptions about component interdependence were too simplistic or my data on lead time variability is insufficient. I can't tell which is the bigger problem. What's the most likely reason for this consistent underestimation, and what's the best next step to improve its accuracy quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often develop mathematical models that perform well with average data but fail to accurately…+
I repeatedly build complex mathematical models that struggle with real-world edge cases.
I often develop mathematical models that perform well with average data but fail to accurately predict outcomes in edge cases or under unusual conditions. This leads to a lack of trust from stakeholders who experience these real-world exceptions. What habit should I change to build more robust and resilient models that account for the full spectrum of real-world variability and uncertainty from the start?
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.