Why Video Courses Don't Stick for DSA and Generative AI

By Pooja Goenka · Published 2026-09-09 · Updated 2026-10-21

Forty hours of DSA videos, three notebooks of notes, and then a two pointer question in a screening round goes badly. The usual explanation is that you didn't practice enough. Often true. It also lets the format off the hook, and the format deserves some of the blame.

I want to be specific about why, because "video bad, interactive good" is a marketing line and I would rather give you something you can check.

The gap between following and doing

A good video explanation is easy to follow, and that ease is exactly what misleads you. Psychologists call it the fluency illusion: when material is presented smoothly, we read our own comprehension off how smooth it felt and overrate how much we have actually learned. Rozenblit and Keil found the same effect outside the classroom with what they named the illusion of explanatory depth. People are confident they understand how a zipper works right up until they are asked to explain it step by step, and then the confidence falls apart.

A recorded lesson is engineered for smoothness. The instructor already knows where the hard part is, has rehearsed the sentence that gets past it, and has cut the twenty minutes where they were confused. You get the clean path and miss the experience of being lost and finding your way out, which is the part that transfers to a problem you haven't seen.

Why video is a bad container for an algorithm

An algorithm is a state machine. It has a current state, a rule for the next step, and a stopping condition. A video is a timeline with a position and a play rate. Those two things do not map onto each other.

You feel it the moment you get stuck. You want to go back one operation, and what you get is a scrub bar that jumps three seconds and drops you mid sentence. You want to hold the frame where the left pointer moved and stare at it for a minute, and the narration keeps going. You want to change the input array to see whether your theory about the loop invariant survives, and you can't, because it is a video of an array.

Cognitive load researchers have a name for the underlying problem too: the transient information effect. Narration and animation vanish as they play, so your working memory has to hold every earlier step while processing the current one. A static diagram you can look at twice costs you nothing. This is one of the better replicated results in instructional design, and it points the same way every time. For anything with several interacting parts, people learn more from material that stays on screen than from material that plays.

You can search a page, you can't search a video

Two months later you are revising for interviews and you half remember something about why the slow pointer starts at the head. In a written, visual lesson that is a fifteen second lookup. In a video course it is a rewatch, or a scrub hunt through a forty minute recording where the answer sits somewhere near minute twenty six.

Video runtimes are also chosen for retention curves and ad breaks, so lessons end up the wrong size. An idea might need ninety seconds, or an hour of sitting quietly with one diagram, and very few of them need twenty two minutes.

What this looks like in DSA

Take memoization. The standard line is that you store intermediate results so you don't recompute them. You can repeat that in an interview and get nothing for it, because it describes the fix rather than the problem.

Now draw the call tree for a naive fib(6) and expand it yourself. fib(4) appears twice. fib(3) appears three times. fib(2) appears five times. fib(1) appears eight. Once you have counted the duplicates on your own screen, you have worked out why memoization exists before anyone told you, and you can explain it in the round.

A video shows you that tree for eight seconds on the way to the code, even though the tree is where the understanding comes from.

Most of the DSA topics people find slippery work the same way, whether it is why quicksort's partition step is correct, why a heap is an array, or why BFS gives you the shortest path on an unweighted graph and stops doing that once you add weights. You understand them by watching state change under your own hand, one step at a time, on inputs you chose.

What this looks like in generative AI

The GenAI version is worse, because the vocabulary hides so much.

"An embedding places semantically similar text close together in vector space." Everyone can say that sentence. Very few people who have only watched it explained can tell you what changes when you swap the model, or why "bank" sitting near "river" lands somewhere different from "bank" sitting near "loan", or what "close" is measuring in the first place.

Attention has the same problem. A heatmap over a sentence on a slide is a picture of the answer. Add a token yourself and watch the weights redistribute, and you can start reasoning about why they moved.

The agent loop runs model, tool call, result, model again, until a stop condition fires. On a slide it is four boxes and thirty seconds of narration, and it looks obvious. When you step through it with a real tool that returns a real failure, you see why anyone bothered building LangGraph.

Where video is still the better format

Our team learns from video constantly, and for some things it is the better format.

Video wins when the thing you are learning is a workflow rather than a concept. Watching an experienced engineer set up a project, move around their editor and drive a debugger teaches you a dozen small things nobody ever writes down. It wins on the messy parts too. A live debugging session where the first three theories are wrong teaches a lot, and it is exactly the footage a polished course cuts.

Some days you also just want a human voice and no decisions, which is a fair reason to press play. I would rather you started badly than not at all.

A study loop that works for both

Whatever course you end up using, the shape that works is roughly this:

1. Watch the thing move before you read about it, so you have a picture of the state changing.
2. Predict the next step before you reveal it. This is where the learning happens and it is the step everybody skips.
3. Write the code yourself from a blank file, rather than editing someone else's.
4. Get it checked immediately, while you still remember what you were thinking.
5. Come back in a week and rebuild it from nothing.

Steps two and five are retrieval practice, which is the best supported finding in this whole area. Roediger and Karpicke's work on the testing effect showed that people who spend study time trying to recall material beat people who spend the same time rereading it, and the gap grows the further you get from the study session, even though rereading is the one that feels more productive at the time.

How the LogicWiz courses are built around this

Both of our courses follow this reasoning. We built them this way because the alternative had not worked for us.

The DSA track has a growing library of curated problems. Concepts arrive as visual simulations and short stories instead of a lecture, then you write the solution in the in browser playground and it is auto judged against the test cases right away. There is XP and a leaderboard, which is a small thing that does measurably get people back the next day. When you are stuck, the AI chat gives you a nudge rather than the answer. That was a deliberate choice and an irritating one to build.

The Generative AI course is a growing library of lessons, running from Python basics through retrieval augmented generation, LangGraph orchestration, multi agent systems, and what is actually happening inside a transformer. Every lesson pairs written material with an in browser lab, and there is an AI tutor you can interrupt in the middle of a lesson. The early chapters need no account and no card, on purpose, because an hour is enough to work out whether this format suits you.

The Generative AI course is completely free, and the DSA track is free while we are pre launch.

For workflows, a good video course still has its place. This format is for the part video handles worst, sitting inside a mechanism and poking at it until it makes sense.

Common questions

Is visual learning actually better, or is this the learning styles myth?

These are two different claims. The learning styles idea, that you are a "visual learner" and your friend is an "auditory learner" and you each need different material, has not survived testing. My argument is about the subject, and it applies to every learner. Algorithms and model internals are things with states and flows, so material that shows state changing fits them better than material that describes it, and that holds for everyone, including people who are certain they learn best by listening.

Can I learn DSA without watching any videos?

Yes, and most people who get good at it end up spending the bulk of their time in a problem editor rather than a video player. Videos are useful for a first pass at an unfamiliar topic. The reps are what carry you through a screening round.

How long does it take to become interview ready?

That depends on where you start and how consistent you are, and anyone giving you a number in weeks is guessing. A more honest measure is problems solved from scratch with no hints. When you can read an unseen medium problem and know within two minutes which shape it is, you are close.

Do I need Python before starting the generative AI course?

No. It begins at Python basics and builds up to agentic systems across all the lessons. If you already write Python, skip ahead. Nothing later is locked behind lessons you passed over.

Is it genuinely free?

The early GenAI chapters need no signup and no card. Later chapters need a free account. The GenAI course is completely free, and the DSA track is free while we are pre launch. Current terms are on the pricing page.

What should I do if I have already bought a video course?

Finish it, but change how you use it. Watch a segment once at normal speed, close it, and rebuild the idea in a code editor or on paper without looking. If you can't, go back to the exact minute you needed. You will get far more out of the same course, and you will find out quickly which parts you only thought you understood.

Start the DSA track or the Generative AI course. The early GenAI chapters need no signup, so you can tell within an hour whether this way of learning suits you.

For a side-by-side of the free options for DSA, see free ways to learn and practise DSA, compared.