How to revise GATE playlists without rewatching them

If you are preparing for GATE CSE, you have probably watched the big YouTube playlists once already: DBMS, Theory of Computation, Operating Systems. The problem now is revision. You remember that a lecturer explained something, but not which of 90 videos or which minute, and rewatching costs days. I checked the length of a few popular playlists on 20 October 2026:

At 2x speed, the 100-hour DBMS playlist is still 50 hours, and that is before you solve a single question. GATE 2027 is scheduled for February 6, 7, 13, 14, 20 and 21, about 15 weeks from now (dates from IIT Madras; confirm on gate2027.iitm.ac.in). Revising by rewatching is the slowest way to use that time.

You don't need to watch whole videos again. Turn the topics you are shaky on into written notes with timestamps, read them in a fraction of the video's time, and open the video only at the exact minute where something is still unclear. If you are only starting a subject now, the same steps work, and you simply read first and watch less.

I build Unwatch, which turns YouTube videos into written lessons, so I'll say where a tool helps and where it doesn't. The method works without any tool.

1. Find your weak topics first

Pick one subject, say DBMS. Attempt 15 to 20 previous-year questions on it, with no lecture first. Mark what you got wrong or couldn't start. Those topics are your revision list, and everything else can wait. Retrieval attempts before study are well supported by research on learning (for example, Roediger and Karpicke's 2006 paper on test-enhanced learning), and they tell you where the gaps are.

2. One playlist per subject

Pick one channel for each subject and stay with it. Switching between teachers on the same topic costs time and mixes notations. Choose by language and teaching style, not by subscriber count. Sample two or three videos from different channels, then commit.

3. Read the notes, then watch only where you're stuck

For a topic on your list, read a written version of the lecture instead of rewatching it (or before you watch it, if you haven't yet). It is faster to scan, you can search it, and you find out which parts you already know. A 21-minute lecture on functional dependencies, for example, reads in about 10 minutes (see the example below). Then watch only the parts you still don't follow. A lesson with timestamps makes this easy, because each section links to the exact minute in the video.

You can do this without a tool, using the video's transcript and your own notes. The point is to read, then watch selectively.

4. Work the problems by hand before you look at the solution

The mistake I see most is watching someone solve a problem and feeling that you understand it. When the lecturer puts a table on the board, copy it, solve it yourself, and then compare. Where your answer differs is where the learning happens.

5. Test yourself, then come back

After each topic, answer questions without looking: flashcards for definitions, and a few previous-year questions for application. Come back to the same topic after a day, a few days and a week. A common schedule is day 1, day 3 and day 7. Whatever you get wrong goes back on the list, and you rewatch only that part.

An example you can look at

I made a lesson from a free, CC BY-licensed GATE DBMS lecture: Himanshu Kaushik's Functional Dependencies (DBMS 15). The written lesson has the definition, the table from the video, each dependency tested row by row, and the exam-style problems at the end, with timestamps and a quiz and flashcards. The lesson is AI-made, so check the worked answers yourself before relying on them.

Where a tool helps, and where it doesn't

It helps with the reading step: a searchable lesson in the video's order, timestamps to jump to the part you need, and a tutor to explain one step differently. It doesn't replace solving problems yourself, and it can make mistakes, so treat it as a first pass and check anything that matters against the lecture.

It also has a limit I should be honest about. A paid Unwatch plan covers about 28 hours of video a month, so it is meant for the topics on your revision list, not for turning a 100-hour playlist into text. That is the same advice as the method above: you shouldn't be watching the whole playlist anyway.

If you try the method, I'd like to hear which step saved you the most time.