◆ C#

Implement asynchronous operations

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 taskImplement an asynchronous operation for the 'SendEmailNotification' method in the…+
Implement an asynchronous operation for the 'SendEmailNotification' method in the 'NotificationService'. It's currently blocking the main thread, causing UI freezes. Make it non-blocking so the application remains responsive.
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 asynchronous implementation for file uploads, review it for proper error…+
Before I commit this asynchronous implementation for file uploads, review it for proper error handling, cancellation support, and potential race conditions, and suggest improvements to make it more resilient and robust under heavy concurrent usage.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI tried to make our 'GenerateMonthlyReport' process asynchronous to improve responsiveness, and…+
I tried to make our report generation asynchronous, and now I'm getting deadlocks and corrupted data.
I tried to make our 'GenerateMonthlyReport' process asynchronous to improve responsiveness, and now I'm getting intermittent deadlocks and corrupted report data. The finance director needs accurate reports by end of day. I'm afraid I've introduced subtle threading issues or resource contention that I don't understand, and I don't know how to reliably debug these concurrent problems. What's the likely diagnosis for this kind of async failure, and what's the best next move to stabilize the report generation without causing further data integrity issues?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI repeatedly struggle with correctly implementing asynchronous patterns, leading to subtle…+
I repeatedly struggle with correctly implementing asynchronous patterns, leading to concurrency bugs.
I repeatedly struggle with correctly implementing asynchronous patterns, leading to subtle concurrency bugs, deadlocks, or unexpected behavior that are incredibly hard to debug. This costs me significant time and introduces instability. What habit should I change in my approach to designing and implementing asynchronous operations to avoid these common pitfalls and build more reliable concurrent systems?
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.