◆ C#

Automate recurring work tasks

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 taskWrite a C# script that backs up all log files from the production server to our Azure blob…+
Write a C# script that backs up all log files from the production server to our Azure blob storage every night at 2 AM, rotating out anything older than 30 days.
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 this log backup script, make sure it handles network interruptions gracefully…+
Before I deploy this log backup script, make sure it handles network interruptions gracefully and retries failed transfers without losing data, and sends me an email if it fails completely.
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 new log backup script failed last night, but the error message is generic and I can't tell…+
The new log backup script failed last night, but the error message is generic.
The new log backup script failed last night, but the error message is generic and I can't tell if it was a permissions issue, a storage key problem, or a network timeout. The lead developer is out, and I need to get this fixed before the end of the day because we can't lose another day of logs. What's the most likely cause, and what's the quickest way to diagnose it without bringing down the server?
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 spending too much time debugging recurring automation failures from vague error…+
I keep spending too much time debugging recurring automation failures from vague error messages.
I keep spending too much time debugging recurring automation failures from vague error messages. I need to make sure my scripts always provide clear, actionable diagnostics, especially for common issues like network problems or access denied. What habit should I change to ensure my automation scripts are more robust and self-diagnosing from the start?
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.