◆ C#

Prevent common C# mistakes

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 taskReview the 'CalculateDiscount' function in the PricingEngine class for common C# null reference…+
Review the 'CalculateDiscount' function in the PricingEngine class for common C# null reference exceptions. Ensure all input parameters are validated and return 0 if an invalid discount code is provided.
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 commit this, check the 'UserAuthenticationService' for common C# security…+
Before I commit this, check the 'UserAuthenticationService' for common C# security vulnerabilities and performance anti-patterns. Flag anything that could lead to data leaks or slow down login times for our 100,000 users.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA user reported incorrect account details after saving, but our database logs show the update…+
We just had a user report their account details were incorrect after saving, but the logs show success.
A user reported incorrect account details after saving, but our database logs show the update succeeded. I'm afraid of a data corruption issue or an unhandled exception silently failing. The team is already stretched, and I can't afford a major rollback. What's the most probable cause, and what's the quickest way to verify data integrity for that user?
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 fixing small, easily preventable C# errors in production, like null reference exceptions…+
I frequently find myself fixing simple C# mistakes that lead to production issues.
I keep fixing small, easily preventable C# errors in production, like null reference exceptions or incorrect type conversions. It's embarrassing and wastes valuable time. What habit should I adopt in my daily coding or review process to catch these common C# mistakes before they ever reach 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.