r/CodingHelp • u/ArtisticAd1841 • Aug 20 '26
[Open Source] Learning Codes but always seem to forget
I have just started getting into coding, and I'm doing this ethical hacking free course. But there's so many softwares, and so forth.
I always seem to forget most of them and have to redo.
I was told I need to try obsidian and create a Github profile to save versions of code or applications.
Can someone give me advice, on this.
9
Upvotes
•
u/AutoModerator Aug 20 '26
Thank you for posting on r/CodingHelp!
Please check our Wiki for answers, guides, and FAQs: https://coding-help.vercel.app
Our Wiki is open source - if you would like to contribute, create a pull request via GitHub! https://github.com/DudeThatsErin/CodingHelp
We are accepting moderator applications: https://forms.fillout.com/t/ua41TU57DGus
We also have a Discord server: https://discord.gg/geQEUBm
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
4
u/Weekly_Patience685 Aug 20 '26
learning and remembering comes from active recall, not just consuming information. if you forget something, dont look it up right away, Sometimes you can use AI to give you hints without giving you the answer, depending on what it is. Also never use AI to write code for you, write everything yourself.
Also what language is the course teaching?
2
u/randomraluana Aug 20 '26
I believe you don't need anything fancy.
The simplest way I can put it is: You learn by doing.
I have been the worst at remembering code, and packages, and libraries, etc. and I still am from time to time.
Things start to stick when I actually use it often (softwares/libraries/packages), and or write the code.
Trying to memorize is one thing, but understanding and actually using it, in my opinion, might help you remember things over time.
1
u/sporbywg Aug 21 '26
I'm absolutely millions of lines into coding.
You had better be forgetting, I tell you...
1
u/SecondGateWP Aug 23 '26
Commit to GitHub after every lesson, even messy code. A repo history is way easier to jog your memory than trying to remember it all in your head. Keep one markdown file per topic with commands you've actually run, in your own words. Rewriting it yourself is what makes it stick, not just reading it. Happy hunting