◆ MATLAB

Iterate through struct fieldnames

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 taskLoop through all the fieldnames in the 'patient_record' struct and print each fieldname and its…+
Loop through all the fieldnames in the 'patient_record' struct and print each fieldname and its corresponding value.
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 acceptI need to process each field in the 'configuration_settings' struct. For each field, if its…+
I need to process each field in the 'configuration_settings' struct. For each field, if its value is a string, I want to convert it to lowercase, but if it's a numeric value, I want to ensure it's positive, so all settings are normalized before being applied.
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 iterating through the fields of 'experiment_results', but some fields, like…+
I'm trying to iterate through a struct, but some fields are nested structs themselves.
I'm iterating through the fields of 'experiment_results', but some fields, like 'sensor_calibration', are actually nested structs. My current loop is failing to access the values within these nested structures, throwing an error. I'm afraid I'll have to write a separate, complex recursive function, which feels like overkill for this. I can't tell if there's a simpler, more direct way to handle this. What's the best next move to correctly access all values, including those in nested structs?
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 and introduce errors when trying to iterate through struct fieldnames,…+
I keep getting stuck when processing complex data structures.
I consistently lose time and introduce errors when trying to iterate through struct fieldnames, especially when dealing with nested structures or needing to perform different operations based on the field's data type. This makes my data processing scripts brittle. What habit should I change to reliably and efficiently iterate through struct fieldnames, ensuring I handle all cases without constant debugging?
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.