◆ C#

Calculate first day of month

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 any DateTime object and returns the first day of that…+
Write a C# function that takes any DateTime object and returns the first day of that month.
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 'first day of month' logic to production for the billing system, ensure…+
Before I deploy this 'first day of month' logic to production for the billing system, ensure it's performant and handles time zones correctly. A small lag could impact thousands of billing calculations, and incorrect time zones could lead to incorrect billing cycles.
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 monthly report is showing the first day of the month as midnight UTC, but the users…+
The new monthly report is showing the first day of the month as midnight UTC, but the users expect their local time zone.
The new monthly report is showing the first day of the month as midnight UTC, but the users expect their local time zone. I didn't specify a time zone, assuming it would default. I'm afraid this will cause confusion for the international team, and I can't tell them it's 'technically correct'. What's the likely reason for the UTC default, and what's the best way to ensure it reflects the user's local time zone?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently forget to account for time zones when dealing with dates, leading to subtle bugs…+
I frequently forget to account for time zones when dealing with dates, leading to subtle bugs and user confusion.
I frequently forget to account for time zones when dealing with dates, leading to subtle bugs and user confusion, especially with 'start of day' or 'end of day' calculations. This costs me time in debugging and fixing. What habit should I change to consistently remember time zone considerations in date logic?
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.