Section checkpoint

Prompt Engineering

10 questions drawn from the 5 chapters in this section. If most land on the first try, you are ready for the next section. If not, the explanation after each answer says which idea to revisit.

Checkpoint

10 questions · first-try answers earn the most XP

1. Why does the chapter insist prompts should be versioned and A/B tested?

2. Why do few-shot examples outperform a paragraph of rules about the same task?

3. What does the chapter mean by "delete one line and watch reliability drop"?

4. Why does the chapter call a prompt "the cheapest code you will ever ship"?

5. Why is curating the *tricky* few-shot examples more valuable than adding easy ones?

6. Which problem is chain-of-thought a poor fit for?

7. Why separate duties, so the agent that reads untrusted content does not hold the refund button?

8. Why should you keep an attack set and run it as part of your evals?

9. An agent is about to delete a customer record. The chapter says to gate this on what, rather than the model's judgement?

10. What does "assume the system prompt can leak" change about how you build?

What this checkpoint covers

Next section: Embeddings, Vector Search & RAG