◆ C#

Print a size_t variable portably

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 print the `itemCount` variable, which is a `size_t`, to the console. Make sure it…+
I need to print the `itemCount` variable, which is a `size_t`, to the console. Make sure it prints correctly on both 32-bit and 64-bit systems.
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 commit this `size_t` printing logic, make sure it's not going to cause compiler…+
Before I commit this `size_t` printing logic, make sure it's not going to cause compiler warnings or truncation issues on different architectures. Flag any potential portability problems.
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 tried to print `totalBytes` using `%d` and the compiler warned me about an incompatible…+
I'm trying to print a `size_t` variable and it's giving me a warning about format specifiers.
I just tried to print `totalBytes` using `%d` and the compiler warned me about an incompatible type. I'm afraid of silent data corruption if I just cast it, but I also need this build to pass. Is there a standard, safe way to print `size_t` that I'm missing, and what's the best immediate fix?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI always lose time trying to remember the correct, portable format specifier for `size_t`…+
I keep having to look up the right way to print `size_t` for portability.
I always lose time trying to remember the correct, portable format specifier for `size_t` across different compilers and architectures. It feels like a trivial thing, but I keep getting it wrong or having to double-check. What habit can I change to make this less of a recurring mental block?
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.