◆ MATLAB

Build automation files

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 MATLAB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskTake the 'data_processing_pipeline.m' script and package it into an executable that my…+
Take the 'data_processing_pipeline.m' script and package it into an executable that my colleagues can run without having to install the full software. Include all necessary dependencies so it works out of the box for the team.
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 share this data analysis tool with the lab, build a robust automation file for it. It…+
Before I share this data analysis tool with the lab, build a robust automation file for it. It needs to handle different input file types gracefully, provide clear error messages if something goes wrong, and generate a summary report automatically at the end for Dr. Evans.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'ingest_sensor_data.m' script, which processes incoming sensor feeds, is failing about 10%…+
The new automation script for data ingestion is intermittently failing.
The 'ingest_sensor_data.m' script, which processes incoming sensor feeds, is failing about 10% of the time, often late at night. The error messages are vague, and I can't reproduce it consistently during the day. We need this data for the morning stand-up, and I'm afraid of missing critical information. Is it a race condition, or an external dependency? What's the best way to add logging and error handling to pinpoint these intermittent failures without disrupting the live feed?
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 find myself with multiple versions of the same script, like 'experiment_v1.m',…+
I frequently struggle with managing different versions of my research code and sharing it.
I often find myself with multiple versions of the same script, like 'experiment_v1.m', 'experiment_v2_final.m', and 'experiment_v2_final_fixed.m'. This makes it impossible to track changes, collaborate with Sarah, or revert to a known working state. What habit should I change to manage my code versions more effectively and ensure I can easily share and merge changes with my team?
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.