◆ C#

Pass a function as a parameter

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 taskPass the 'logMessage' function to the 'ProcessBatch' method, so 'ProcessBatch' can record its…+
Pass the 'logMessage' function to the 'ProcessBatch' method, so 'ProcessBatch' can record its progress without needing to know the logging implementation details.
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 finalize the 'ProcessData' function, refactor it to accept a callback for handling…+
Before I finalize the 'ProcessData' function, refactor it to accept a callback for handling completion. This way, different modules can react to the data processing finishing without 'ProcessData' needing to know their specific logic, making it more reusable.
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'm trying to implement a plugin system where users can define custom validation rules for…+
I need to allow a user-defined validation rule to be applied dynamically, but I'm stuck on the best pattern.
I'm trying to implement a plugin system where users can define custom validation rules for incoming data, but I can't figure out how to pass these rules into my core processing pipeline dynamically. I'm afraid of creating a tightly coupled mess or a security vulnerability. How can I safely pass and execute these user-defined functions as parameters without compromising stability or performance?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy utility and helper functions always end up tightly coupled to the calling code, making them…+
My helper functions always end up tightly coupled to the calling code.
My utility and helper functions always end up tightly coupled to the calling code, making them hard to reuse or test independently. I find myself duplicating logic just to avoid pulling in too many dependencies. What habit can I change to consistently design functions that accept necessary behavior as parameters, making them more flexible and less dependent on their callers?
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.