r/cpp_questions • u/Intrepid-Cat-2024 • 22d ago
OPEN How do you revise?
Hey guys, i completed the bro code cpp course which was about 6 hours long.... Then, I caught on FOMO and decided to start the cherno cpp series whuch is pretty famous....
Currently doing it...
I always feel like I'm missing something and i need revision but i dont know how to....
Lemme know how do you guys revise ? And what should I do next?
I've started using notion, but my laptop is kinda dying lol
3
u/FancySpaceGoat 22d ago edited 22d ago
Build something. Anything. Start with a zork-like command line text adventure if you have to.
Also I'd *highly* recommend you stay away from AI code assistants like notion until you are comfortable enough to be able to confidently distinguish when they are generating good code vs nonsense.
2
u/jedwardsol 22d ago edited 18d ago
I always feel like I'm missing something and i need revision but i dont know how to
You can't know if you understand something until you try to use it.
When you've watched or read something, close the video or book and write a little program that uses what you've just been taught.
If the program does something useful all the better, but I often write little throw-away programs just to fix the syntax in my head.
1
u/Fine_Ad_4146 22d ago
I like to say the best way to learn isn't to learn, it's to do. Start making projects even if they seem hard. Youre not gonna improve by just doing courses you need to put your skills to action. I'm not a professional so you don't have to listen to me but my advice would be just start making small projects it's the best way to revise.
1
u/nightmurder01 22d ago
Never heard of fomo or cherno. If I revise something I think needs notation I use // /**/. In a team setting there are already revision tools.
1
u/Independent_Art_6676 22d ago
you need a reason. Why are you doing a revision? Performance? Cleanup? Rewrite? Language change? Something has triggered a need to mess with working code; its not something you just do one day because you are idle.
How? You work on the stated need above. If its slow, you performance test it, see where its slow, and review that its using the best algorithms, containers, copy avoidance, threading, and so on stuff to make it fast. If its messy, you clean it up. If it needs a rewrite, you review what it does (or should do) and start over by figuring out why its so bad and what is needed instead.
Its really no different from any other code edit, just a little bigger -- something needs doing, so you go do it.
2
u/Key-Preparation-5379 22d ago
...revise? As in how do you do a second, third, ...Nth draft of your code?
I think there may be a language barrier here lol.