Engineers and product people who write prompts that mostly work and want to know why they sometimes do not. It suits anyone shipping an LLM feature, candidates interviewing for AI-adjacent roles, and people who have been iterating prompts by feel without a way to tell improvement from noise.

Each lesson opens with a short set of reading cards on the concepts it covers, then puts you straight into questions. Every question is multiple choice, and a wrong answer returns an explanation immediately — so the mistake becomes the thing you remember rather than something you mean to look up later.

Accuracy is tracked per lesson, so after one pass you have a map of which areas you are solid on and which need another round. That matters more here than in a long course: the point of a crash course is to find your gaps quickly, not to grind evenly through material you already know.

The first three lessons — Anatomy of a Prompt, Common Misconceptions and What Prompting Actually Does — are free, with their reading cards and their full question sets. They are a fair sample rather than a teaser: the format, the difficulty and the explanation style are identical to the 31 lessons behind them.

Each lesson is sized for one sitting: a short deck of reading cards, then its question set, typically ten to fifteen minutes. That matters for a crash course — the failure mode of a long syllabus is not difficulty but abandonment, and a lesson you can finish on a commute is a lesson you actually finish.

A video course is measured in hours watched; this is measured in questions answered. Watching someone explain structured-output reliability, evaluation design, and diagnosing whether a failure is the prompt or the model feels productive, but you find out whether you understood it the moment you have to choose between four plausible answers. Recall beats recognition, and questions force recall.

The trade-off is honest — a video series is better when a topic is entirely new to you. That is why this course assumes prior exposure to prompt engineering, and why the full course exists for the areas where you want more room.

There is also a scheduling argument. 306 questions at roughly forty-five seconds each is about 3.8 hours, which fits into a few evenings around a job. A full syllabus at ten questions per sub-concept does not.

The difference is depth, not coverage. Both reach the same areas. This one gives you one merged lesson per cluster and 306 questions; GenAI Engineering: Prompt Engineering breaks the same material into 143 lessons at roughly ten questions each, so you can sit on a single idea until it is automatic. Start here if you are short on time or want to find your gaps, then move to the full course for the areas the gaps turn up in. If you want a different subject at the same pace, Python Crash Course follows the same format.

A conventional syllabus teaches zero-shot, one-shot and few-shot prompting as three lessons, each re-explaining what an example does. Merged, the actual question — how many examples buy how much reliability, and when they stop helping — is answerable in one pass.

A practical order: work straight through without stopping to perfect anything, note the lessons where your accuracy drops below about seventy percent, then do a second pass on only those. Most people find three or four weak areas, and knowing which three is worth more than another ten hours of undirected study.

What this deliberately does not do is teach prompt engineering from nothing. Every lesson assumes the basic vocabulary and spends its questions on the reasoning instead. If that assumption does not hold yet, the full course is the better starting point.