How do you guys tackle massive Udemy/Coursera courses? Do you really watch 100% of it?
Posted by LavishnessIcy2379@reddit | learnprogramming | View on Reddit | 9 comments
Hey everyone, I need some advice on learning strategies.
When following online courses on platforms like Udemy or Coursera, they usually pack in a massive amount of hours. Since everything looks important, I always feel this pressure to complete them 100% from start to finish without skipping a single second. However, I've heard many people say that watching everything isn't necessary or efficient.
The main struggle is that tech updates incredibly fast, so we have to learn quickly. But at the same time, rushing through and just skimming the surface feels useless because you need a solid understanding to actually build things.
I would love to get your perspective:
- What is your most effective approach to learning from these huge courses quickly but properly?
- Do you watch every single video, or do you cherry-pick the sections?
- If you do skip around, how do you ensure you aren't missing core concepts?
Any tips or personal experiences would be really appreciated. Thanks in advance!
BranchLatter4294@reddit
Videos have low information density so they slow down learning a lot. I avoid them except for the short introductory video, where I can then launch my own learning.
opentabs-dev@reddit
honestly the trick that helped me was picking a small project before starting the course and then only watching the parts i needed to unblock it. like if im taking a node course id decide "im building a url shortener" first, then i skip half the section on like fs/path stuff and dive into express/db/auth becuase thats what i actually need. you retain way more when youre using it for something real vs just nodding along to a video. and when i hit something i dont understand i pause and go read the docs for that one specific thing instead of grinding through 3 more lecture videos hoping itll click
Select-Reporter5066@reddit
I’d treat the course as a map, not a checklist. Build something small first, then only go back when a missing concept blocks you.
Scared-Push3893@reddit
trying to fully complete giant courses fried my brain way faster than building stuff lol. now i mostly grab the parts i need and fill gaps later. my notes got messy af from this so ive been throwing everything into Runable to figure out what actually matters
crawlpatterns@reddit
i stopped trying to finish 100% of every course a while ago becuase it honestly burned me out fast. now i usually watch the core sections, build something small with it, then come back later if i get stuck on a concept i skipped before. most of the learning kinda happens when you actually try to make stuff on your own anyway. also tech changes so fast that being able to learn iterativly is probly more useful than perfectly completing every single lesson tbh
appendixexploder@reddit
what's your definition of massive?
PotemkinSuplex@reddit
I took a few specific DataCamp courses with a pretty good idea on r, sql and python to begin with. The parts I did understand I just didn’t watch. As soon as I had any problem with a task that was not resolved by Google searching for 2 minutes, I watched the video.
Most courses are made to be as novice friendly as they can be, which is good, but it can inflate them quite a bit.
EntrepreneurHuge5008@reddit
No. I watch the first few modules to be "introduced," and then it's just cherry-picking or as a reference whenever I don't know something, or don't remember.
Broad_Geologist7998@reddit
Not really. I watch all the content at 2x speed and skip parts of the videos that seem unnecessary.