Are All Courses PowerPoint Slide Dumps? No. But the Default Is Too Slide-Heavy
Slide-heavy courses like Stephane Maarek's are often called video textbooks. Here's how to tell whether a course is a passive info dump or a hands-on build loop.
The question “Are all courses just PowerPoint slide info dumps or just Stephane’s?” usually comes from someone with too many Udemy tabs open and too few terminal sessions. It is a fair question. The short answer is no, but the pattern is real enough that you should learn to spot it.
The “Stephane pattern” is real
Stephane Maarek’s courses are often described in cloud certification communities as “video textbooks.” They are densely produced, slide-first, and optimized for breadth. You get architecture diagrams, service comparisons, limits, and exam tips. That makes them useful references when you need to remember whether an AWS solution uses eventual consistency or strong consistency.
But the format has a trade-off: you can complete dozens of hours without opening a real AWS account, reading a Terraform plan, or troubleshooting a broken security group. That is the line between “slide-supported” and “slide dump.” A slide dump is not bad because it contains slides. It is bad because there is no deliberate practice beneath them.
Why slide-heavy courses dominate
There is a simple economic explanation. Hands-on labs are expensive to build, break when cloud consoles change, and require support when students get stuck. Slides are cheaper to update and scale infinitely. A certification course that covers 150 services can turn into a checklist, and slides are the easiest way to check boxes.
The result is a content coverage model, not a skill acquisition model. That model works for exam cramming because certification exams often reward recall and recognition. It works less well for the first week on the job, when you have to make changes to a real environment and nobody gives you multiple choice options.
The courses that are not slide dumps
The hands-on ecosystem is larger than it seems. Adrian Cantrill’s AWS courses, for example, include mini projects and guided labs that force you to interact with real infrastructure. KodeKloud built its Kubernetes reputation almost entirely on browser-based labs and broken-cluster troubleshooting. Developer platforms like Boot.dev, Exercism, and Codecademy have moved away from video-first formats entirely.
The common pattern is not “no slides.” It is “slides as map, lab as territory.” The course gives enough context to start, then asks you to build, break, and repair something concrete.
How to spot the difference before you buy
Look for evidence of hands-on work in the curriculum. A course that includes GitHub repositories, CloudFormation or Terraform templates, sandbox environments, and explicit “follow along in your own account” exercises is not a pure slide dump. Even stronger signals include: you see an error state on screen, the instructor shows the AWS console or terminal, and the project does not work until you make a decision.
Red flags include wall-to-wall slides, no repository link, no lab section, no cost warnings, and no troubleshooting segments. If the course promises “everything you need to pass” but never asks you to run a command, it is probably a reference library rather than a training program.
From slide dump to build loop
At Sapior, we take a developer-tool view of learning: the terminal is the syllabus. A good course should produce a reusable artifact, not just a completed progress bar. Whether you are learning AWS, Kubernetes, or an internal platform, the test is simple: can you do the task when the instructor stops talking?
Use three questions. Does the course force a decision? Does it show the real failure mode? Does it leave behind code you can reuse? If the answer to all three is no, the production value of the slides does not matter.
Verdict: No, but the default is still too slide-heavy
Stephane Maarek’s courses are not “just” PowerPoint dumps. They are structured, well-edited reference material that helps many people pass exams. But they represent the default mode of cloud education: watch first, build later (or never). That default is the actual problem.
The next time you see a course preview full of polished slides, close the preview and ask: where will I build? If the curriculum cannot answer, you already know what kind of course it is.