◆ MATLAB

Initialize an array of structs

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 taskCreate an array called 'sensorData' where each element is a struct with fields for 'timestamp',…+
Create an array called 'sensorData' where each element is a struct with fields for 'timestamp', 'temperature', and 'pressure'. Initialize it with three entries: first at 1678886400 with 25 degrees and 101.2 kPa, second at 1678886460 with 25.5 degrees and 101.3 kPa, and third at 1678886520 with 26 degrees and 101.1 kPa.
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 hand off this 'experimentLog' struct array to the summer intern, make sure it's easy…+
Before I hand off this 'experimentLog' struct array to the summer intern, make sure it's easy for them to work with. Can you add a 'units' field to each struct, specifying 'Celsius' for temperature and 'kPa' for pressure, and ensure there's an example of how to access the data for the first entry?
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'm trying to create an array of structs for my simulation results, but I'm getting an error…+
I'm trying to create an array of structs for my simulation results, but I'm getting an error about inconsistent field names.
I'm trying to create an array of structs for my simulation results, but I'm getting an error about inconsistent field names when I try to add the fifth data point. Dr. Kim needs this data organized by tomorrow for the conference abstract. I'm afraid I'll have to manually restructure everything if I can't fix this quickly. I don't know if I'm initializing it incorrectly or if there's a better way to append new structs. What's the most likely cause of this field name error, and what's the best next step to fix it without losing data?
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 struggle to efficiently manage and update arrays of structs as my data grows,…+
I consistently struggle to efficiently manage and update arrays of structs as my data grows.
I consistently struggle to efficiently manage and update arrays of structs as my data grows, especially when adding new fields or entries later. This always leads to refactoring headaches and lost time when preparing data for lab meetings. What habit should I change to better anticipate data structure evolution and ensure my struct arrays are robust and easy to modify 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 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.