◆ C#

Write object-oriented code in C

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 taskI need to implement a `Logger` module in C that allows different logging levels (INFO, WARN,…+
I need to implement a `Logger` module in C that allows different logging levels (INFO, WARN, ERROR) and can be configured to output to a file or stdout. It needs to be reusable across multiple parts of the application.
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 share this C code for the `NetworkClient` with the team, make sure it clearly…+
Before I share this C code for the `NetworkClient` with the team, make sure it clearly separates concerns. Is the connection management distinct from the data parsing? Flag any areas where responsibilities are blurred, especially for future maintainability.
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 building a system where I need different 'device' types to have their own `read` and…+
I'm trying to implement a 'virtual' method table in C and it feels overly complex.
I'm building a system where I need different 'device' types to have their own `read` and `write` functions, but I want to call them through a common interface. I'm afraid of creating a spaghetti of function pointers and casting. Is there a more idiomatic C way to achieve this kind of polymorphism without making it unreadable, or am I overthinking the complexity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself wrestling with how to encapsulate data and functions in C to avoid global…+
I frequently struggle with managing complex state and behavior in C without resorting to global variables or huge structs.
I often find myself wrestling with how to encapsulate data and functions in C to avoid global state and improve modularity, especially as a project grows. It feels like I'm constantly fighting the language's nature. What habit should I cultivate to design more maintainable, object-like structures in C from the outset?
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.