◆ C#

Detect unsigned integer overflow

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 taskCheck the C# code in 'DataProcessor.cs' for any potential unsigned integer overflows in…+
Check the C# code in 'DataProcessor.cs' for any potential unsigned integer overflows in arithmetic operations, specifically in the 'CalculateHash' method.
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 new version of the 'PacketParser.cs' module, make sure it's robust.…+
Before I commit this new version of the 'PacketParser.cs' module, make sure it's robust. Analyze the 'ProcessHeader' and 'ValidateChecksum' methods for any unsigned integer overflows that could lead to incorrect calculations, and suggest specific fixes that prioritize correctness over raw speed.
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 debugging a weird issue in 'LogWriter.cs' where our unsigned message IDs are sometimes…+
A customer reported strange, intermittent data corruption in our logging service, only under heavy load.
I'm debugging a weird issue in 'LogWriter.cs' where our unsigned message IDs are sometimes incorrect, but only when the system is under high traffic. I suspect an unsigned integer overflow somewhere in the ID generation or serialization logic, but I can't reliably reproduce it. What's the most likely scenario for an unsigned integer overflow to manifest intermittently under load, and what's the best next step to isolate and confirm it without bringing down the production system?
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 get burned by subtle data corruption or incorrect calculations that, after hours…+
I keep getting surprised by subtle data corruption issues that trace back to unsigned integer overflows.
I frequently get burned by subtle data corruption or incorrect calculations that, after hours of debugging, turn out to be unsigned integer overflows I missed. What habit should I change to systematically identify and mitigate these risks during code review or initial development, especially in performance-critical C# code, rather than discovering them through painful customer bug reports?
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.