◆ C#

Identify performance issues in C#

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 C# tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskProfile the C# backend service for the customer portal, focusing on CPU and memory usage during…+
Profile the C# backend service for the customer portal, focusing on CPU and memory usage during peak load, and identify the top five most expensive methods or code blocks over a 30-minute period.
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 this C# reporting service goes live, analyze its database query patterns. Flag any N+1…+
Before this C# reporting service goes live, analyze its database query patterns. Flag any N+1 queries, unindexed lookups, or excessively complex joins that could cause performance bottlenecks when generating reports for 10,000 users concurrently.
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 C# API endpoint for 'GetOrders' is suddenly very slow, taking over 5 seconds per request,…+
The C# API endpoint for 'GetOrders' is suddenly very slow, impacting user experience.
The C# API endpoint for 'GetOrders' is suddenly very slow, taking over 5 seconds per request, and users are complaining. The sales team needs this fixed by end of day for their quarterly reports. I've checked the database, and it seems fine, but I'm worried it's a recent code change that introduced an inefficient loop or an unoptimized data structure in the C# code itself. What's the most likely cause for this sudden slowdown, and what's the quickest way to pinpoint the exact code section responsible?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time and accuracy, and frustrating users, by reacting to C# performance issues…+
I often find myself reacting to C# performance issues instead of preventing them.
I keep losing time and accuracy, and frustrating users, by reacting to C# performance issues after they hit production, instead of catching them earlier. My code often performs adequately in development but struggles under real load. What habit should I change to consistently identify and address potential performance bottlenecks in my C# applications before they become critical problems?
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.