◆ C#

Analyze data using .NET

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 taskAnalyze the customer support ticket data from the last quarter to identify the top 5 recurring…+
Analyze the customer support ticket data from the last quarter to identify the top 5 recurring issues.
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 present this support ticket analysis, make sure the results are grouped by category…+
Before I present this support ticket analysis, make sure the results are grouped by category and sub-category, show the trend over time for each of the top issues, and include a confidence score for the categorization accuracy since some tickets are ambiguously worded.
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 product manager is questioning the categorization of 'login issues' in my analysis, saying…+
The product manager is questioning the categorization of 'login issues' in my analysis, saying it seems too high.
The product manager is questioning the categorization of 'login issues' in my analysis, saying it seems too high and might be conflating different problems. I used a keyword search, but I'm afraid I might have missed nuances or included unrelated tickets. I need to demonstrate the validity of my findings by tomorrow. What's the best way to quickly sample and validate the categorization of a specific issue category, and what alternative methods could I use to improve accuracy?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI repeatedly find myself defending my data analysis against skepticism about methodology or…+
I repeatedly find myself defending my data analysis against skepticism about methodology or assumptions.
I repeatedly find myself defending my data analysis against skepticism about methodology or assumptions, which erodes trust. I need to make my analytical process more transparent and defensible. What habit should I change to clearly document my assumptions, data cleaning steps, and analytical choices so that my results are more readily accepted and understood?
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 C#'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.