BeginnerCoder

Lesson 3 — Asking for small steps

One step, one check

"Build me a tip calculator app" is a big request. The assistant will write a big answer, and if something is wrong you will not know where.

Better: split the job into small steps and ask for one at a time:

  1. a function that calculates the tip;
  2. a function that splits the bill between people;
  3. rounding to 2 decimals;
  4. printing a receipt.

After each answer you run and test it, and only then ask for the next step. A small answer is easy to read, easy to test, and a bug is always in the last thing you added.

Say it in the prompt too: "Do only this step, then stop." — otherwise assistants often jump ahead and write everything.

Why it matters: small steps turn one big unknowable answer into four small answers you can actually check.

Want it another way?
Task

Write step_prompts(project, steps): return a list of strings like "Step 1/4 for tip calculator: <step>. Do only this step, then stop."

Run your code — when the output matches the task, you will see a green check. Then mark the lesson complete.

← Back
Next →
Test your knowledge

A quick 3-question quiz on this lesson — instant feedback.

Enjoying this lesson? Share it.