◆ C#

Determine CPU and memory consumption

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 taskDetermine the current CPU and memory consumption for the 'ImageProcessor.exe' process running…+
Determine the current CPU and memory consumption for the 'ImageProcessor.exe' process running on this server.
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 deploy the new 'ReportGenerator' service, give me a performance baseline. Run it for…+
Before I deploy the new 'ReportGenerator' service, give me a performance baseline. Run it for 30 minutes under a simulated load of 50 concurrent requests, and report its average CPU usage, peak memory consumption, and identify any significant memory leaks or CPU spikes that exceed 80% utilization.
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 'DataAggregator.exe' service is reportedly spiking CPU to 100% and consuming all available…+
The ops team is screaming that our 'DataAggregator' service is making the server unresponsive every afternoon.
The 'DataAggregator.exe' service is reportedly spiking CPU to 100% and consuming all available memory on the production server every day around 2 PM, making other services unresponsive. I can't pinpoint what's causing it. What's the most likely scenario for a C# service to suddenly consume all resources like this, and what's the best next move to quickly identify the specific code path or operation causing the spike without having to restart the service during peak hours?
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 getting surprised by new C# services consuming far more CPU and memory than expected…+
I frequently deploy new C# services only to discover they have hidden performance hogs.
I keep getting surprised by new C# services consuming far more CPU and memory than expected after deployment, leading to emergency fixes and lost credibility with the ops team. What habit should I change to proactively profile and benchmark my C# applications for CPU and memory consumption during development, especially under realistic load conditions, so I can catch these issues before they hit production?
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.