◆ C#

Update entities in a database

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 taskUpdate the Customer table in the database. For Customer ID 12345, change their 'Status' to…+
Update the Customer table in the database. For Customer ID 12345, change their 'Status' to 'Active' and their 'LastInteractionDate' to today's date, then save the changes.
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 push these entity updates to production, check if there are any potential data…+
Before I push these entity updates to production, check if there are any potential data integrity issues or foreign key violations that could break existing relationships, and suggest a safer way to structure the update.
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 just ran a batch update on the Product table, trying to set 'Discontinued' to true for all…+
I just ran a batch update on the Product table and the application crashed immediately.
I just ran a batch update on the Product table, trying to set 'Discontinued' to true for all items from Supplier 789, and the application crashed immediately. I'm afraid I've corrupted the data or locked the table. The procurement lead is breathing down my neck for the report. What's the likely diagnosis for this kind of crash, and what's the best next move to recover or at least minimize downtime?
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 losing time, credibility, and accuracy trying to manually synchronize data between our…+
I keep losing time trying to manually synchronize data between our staging and production environments after schema changes.
I keep losing time, credibility, and accuracy trying to manually synchronize data between our staging and production environments after schema changes. It feels like I'm always forgetting a column or missing a script, leading to inconsistencies. What habit should I change to ensure these database updates are consistently applied and verified across environments without constant firefighting?
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.