◆ JavaScript

Implement power function

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
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a JavaScript function called 'power' that takes two arguments, 'base' and 'exponent', and…+
Write a JavaScript function called 'power' that takes two arguments, 'base' and 'exponent', and returns 'base' raised to the power of 'exponent'.
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 implement the 'power' function for our new scientific calculator, ensure it handles…+
Before I implement the 'power' function for our new scientific calculator, ensure it handles both positive and negative exponents, returns 1 for an exponent of 0, and can efficiently calculate large powers without hitting recursion limits or floating-point precision issues.
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 implemented a 'power' function, but it's giving incorrect results for negative exponents…+
I just implemented a 'power' function, but it's giving incorrect results for negative exponents and large numbers.
I just implemented a 'power' function, but it's giving incorrect results for negative exponents and large numbers, specifically when calculating 2 to the power of -3 or 100 to the power of 1000. I'm afraid I've overlooked edge cases or chosen an inefficient algorithm, but I can't tell the team it's not working. What's the most likely diagnosis for these types of errors in a power function, and what's the best next step to debug and correct it without starting from scratch?
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 losing time writing common utility functions from scratch, like 'power' or…+
I keep writing utility functions from scratch that already exist in standard libraries.
I'm constantly losing time writing common utility functions from scratch, like 'power' or 'debounce', when robust, optimized versions already exist in standard libraries. This often introduces subtle bugs and adds unnecessary code. What habit can I change to ensure I consistently check for and leverage existing library functions before attempting to implement them myself, perhaps by doing a quick search in MDN or Lodash first?
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 JavaScript'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.