◆ MATLAB

Generate random 2D polygon

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 taskGenerate a random 2D polygon with 7 vertices for testing the collision detection algorithm.…+
Generate a random 2D polygon with 7 vertices for testing the collision detection algorithm. Make sure the vertices are within the range of -10 to 10 for both x and y coordinates.
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 a random 2D polygon for my collision detection test. Can you generate one with 6 to 10…+
I need a random 2D polygon for my collision detection test. Can you generate one with 6 to 10 vertices, ensuring it's convex and its centroid is near the origin, so it's a good test case without being overly complex or degenerate?
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 generated a random polygon for the simulation, but it ended up with self-intersections,…+
The random polygon I generated for the simulation had self-intersections, which broke the physics engine.
I just generated a random polygon for the simulation, but it ended up with self-intersections, which completely crashed the physics engine. I need a valid, non-self-intersecting polygon with 8 vertices, but I'm not sure how to guarantee that with random generation. Is there a quick way to ensure it's simple or should I manually check and adjust the vertices, which will take too long before the Friday deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently generate random geometries for simulations or tests, only to find they are invalid…+
My random geometry generation often produces invalid shapes, leading to downstream errors and wasted time.
I frequently generate random geometries for simulations or tests, only to find they are invalid (self-intersecting, degenerate, etc.) which then causes errors in subsequent steps. This means I waste time debugging geometry instead of the actual algorithm. What habit should I change to ensure the randomly generated shapes are always valid and useful for their intended purpose, without having to manually inspect each one?
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.