◆ Salesforce

Initialize a Map<String, Integer>

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 taskInitialize a new map called 'opportunityStageCounts' that will store the count of opportunities…+
Initialize a new map called 'opportunityStageCounts' that will store the count of opportunities for each stage name. Make sure it's empty to start.
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 start populating this map, set it up so that it can hold string keys for the stage…+
Before I start populating this map, set it up so that it can hold string keys for the stage names and integer values for their counts. I need it ready to track how many deals are in 'Prospecting', 'Qualification', and so on.
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 add 'New Business' with a count of 5 to my opportunity stage map, but it…+
I'm trying to count opportunities by stage, but my map is throwing a null pointer exception when I try to put the first entry.
I just tried to add 'New Business' with a count of 5 to my opportunity stage map, but it crashed. I thought declaring `Map<String, Integer> opportunityStageCounts;` was enough, but it seems I missed a step. What's the right way to make sure the map is actually ready to store values without error, and what's the best next step to get my first entry in?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly running into null pointer exceptions when I try to use maps or lists right after…+
I keep forgetting to properly instantiate collections, leading to runtime errors.
I'm constantly running into null pointer exceptions when I try to use maps or lists right after declaring them. It wastes time debugging simple setup issues. What habit can I change to ensure all my collections are properly initialized and ready for use from the start, especially when I'm under pressure to deliver a quick fix?
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 Salesforce'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.