◆ C#

Debug and fix code 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 taskDebug the 'CalculateOrderTotal' method in the 'OrderProcessor' class. The current behavior is…+
Debug the 'CalculateOrderTotal' method in the 'OrderProcessor' class. The current behavior is returning incorrect totals when discount codes are applied. Find the bug and fix it so the totals recalculate correctly.
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 submit this bug fix for the 'Login' module, review it for any potential side effects…+
Before I submit this bug fix for the 'Login' module, review it for any potential side effects or new vulnerabilities it might introduce, especially regarding session management, and suggest improvements to make it more robust.
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 client is reporting intermittent 'timeout' errors on a critical API endpoint,…+
The client is reporting intermittent 'timeout' errors on a critical API endpoint, but I can't reproduce it in dev.
The client is reporting intermittent 'timeout' errors on a critical API endpoint, 'api/v2/processPayment', but I can't reproduce it in dev. The logs are vague, showing only 'request timed out' without specific exceptions. I'm afraid it's a race condition or a resource leak that only manifests under heavy load, and the sales team needs a fix by Friday. What's the likely diagnosis for this kind of elusive bug, and what's the best next move to pinpoint the root cause without impacting production further?
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 pulled into urgent production bug fixes that could have been caught earlier in…+
I keep getting pulled into urgent production bug fixes that could have been caught earlier.
I keep getting pulled into urgent production bug fixes that could have been caught earlier in development or testing. It's impacting my ability to deliver new features and making me feel constantly reactive. What habit should I change in my debugging and testing workflow to catch these critical issues before they ever reach production and cause customer complaints?
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.