◆ C#

Troubleshoot common C# problems

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 taskExamine the C# application logs from the production server for the past 24 hours, specifically…+
Examine the C# application logs from the production server for the past 24 hours, specifically looking for unhandled exceptions related to database connectivity or external API calls, and summarize the top three 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 hand off this C# module to QA, analyze its error handling. Point out any places where…+
Before I hand off this C# module to QA, analyze its error handling. Point out any places where exceptions are caught too broadly, swallowed, or where critical information isn't being logged, which could make future troubleshooting difficult for the support team.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers are reporting intermittent 'object reference not set to an instance of an object' errors…+
Users are reporting intermittent 'object reference not set' errors in the C# web application.
Users are reporting intermittent 'object reference not set to an instance of an object' errors in the C# web application, especially during peak hours. The error isn't consistently reproducible, and the logs are only showing generic messages. Our project manager, David, is pressuring for a quick fix because it's impacting sales. I suspect it's a race condition or a null value coming from an external service that I'm not properly guarding against. What's the most likely source of this intermittent null reference, and what's the fastest diagnostic approach to pinpoint it without deploying new code to production?
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 credibility when troubleshooting intermittent C# production issues,…+
I often struggle to quickly diagnose intermittent C# production issues.
I keep losing time and credibility when troubleshooting intermittent C# production issues, especially those that are hard to reproduce. I often feel like I'm chasing ghosts, leading to long resolution times and frustrated stakeholders. What habit should I change to more effectively and systematically diagnose these elusive 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.