r/learnprogramming • u/OkRush4237 • 1d ago

How to ?

Hi guys, I am not understanding how to actually use the GitHub repository project-based learning , that repository with projects for each language and like how can I actually use it effectively and like these have already done projects and like I feel that I am learning nothing.

SO,

Should I see the project idea , let say like in the C/C++ section, I will choose Debugger and like using that idea, I will research and how to create my own debugger ?

Can you please help me with this

3 Upvotes

67% Upvoted

7 comments sorted by

3

u/RequirementGuide 1d ago

I've been through that exact repo before. What worked for me was picking the smallest project in the list, trying to build it myself first without looking at anything, and only then peeking at the tutorial to compare. If you just follow along start to finish, you end up copying without thinking. A debugger is pretty ambitious as a first pick though. I'd grab something tiny like a text editor or a URL shortener first, then work up to the bigger ones.

1

u/OkRush4237 1d ago

Thanks for your advice.. Actually, I didn't know what to do and you helped me .. Thanks a lot

1

u/pastel_enlightenment 16h ago

Pick a specific tutorial from the repo, open it in one window and your editor in another. Build step 1 by reading only the instruction, not the code. If you get stuck on that step for more than an hour, look at their solution just to see what line you missed. Then close their tab and type it yourself. Do this until the whole project runs. You are learning how to read documentation and debug because you cannot copy paste blindly anymore. Start with something tiny like a to-do list or a basic HTTP server so you can finish it before losing interest

1

u/Existing_Put6385 15h ago

Yeah, that's the right idea. Pick one project you actually find interesting, write down what the finished thing should do, and try to build it yourself first. The linked tutorial in the repo is for when you're stuck, not something to follow from the start, so you're not just copying code. Start with the smallest working version, like a debugger that just runs a program and stops at one breakpoint, then add features one at a time. You'll hit walls and have to search things, and that part is where the learning happens. If it feels like too much, start with a smaller project from the same list.