◆ MATLAB

Normalize a histogram

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskNormalize this histogram so the sum of the bin heights equals one. Make sure the x-axis labels…+
Normalize this histogram so the sum of the bin heights equals one. Make sure the x-axis labels are still readable after the change.
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 send this histogram to Dr. Evans for review, make it easier to interpret the…+
Before I send this histogram to Dr. Evans for review, make it easier to interpret the probabilities. Normalize it and clearly label the y-axis as 'Probability Density' so he doesn't have to guess.
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 just normalized the histogram for the sensor data, and the shape seems off. I'm afraid I've…+
The normalized histogram I just generated looks wrong, and I'm worried it's skewing my entire analysis.
I just normalized the histogram for the sensor data, and the shape seems off. I'm afraid I've made a fundamental error that will invalidate my results for the grant report due tomorrow. I can't tell if it's a scaling issue or if the underlying data is actually distributed this way. What's the most likely reason for a distorted normalized histogram, and how can I quickly check if my normalization method is correct?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently lose time double-checking normalization on plots before every presentation to…+
I keep spending too much time manually checking if my plots are correctly normalized for presentations.
I consistently lose time double-checking normalization on plots before every presentation to the project team. I'm worried about presenting incorrect relative frequencies. What habit could I change to ensure my histograms are always correctly normalized and clearly labeled without constant manual verification?
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 MATLAB'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.