◆ C#

Calculate week numbers from dates

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
See the prompt↓All C# tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a C# function that takes a DateTime object and returns the ISO week number for that…+
Write a C# function that takes a DateTime object and returns the ISO week number for that date.
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 use this week number calculation in the financial reporting, make sure it's reliable…+
Before I use this week number calculation in the financial reporting, make sure it's reliable for all edge cases. Test it with dates around year-end, especially those spanning different ISO week years, to prevent misreporting Q4 numbers.
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 finance team is saying the week numbers in the new report are off by one for some dates in…+
The finance team is saying the week numbers in the new report are off by one for some dates in January.
The finance team is saying the week numbers in the new report are off by one for some dates in January. I used a standard .NET method, but I'm afraid it's not the ISO standard they expect, and I can't tell them I just used the first thing I found. What's the likely discrepancy, and what's the quickest way to confirm and fix it?
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 tripped up by date calculations that seem simple but have subtle international…+
I keep getting tripped up by date calculations that seem simple but have subtle international differences.
I keep getting tripped up by date calculations that seem simple but have subtle international differences, leading to embarrassing corrections with stakeholders. This always happens with week numbers and fiscal periods. What habit should I change to avoid these 'obvious but wrong' date calculation errors?
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.