42
How does one code by themself?
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Jul 2026
42 points (100.0% liked)
Programming
28138 readers
307 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Repetition is key here. And solving problems.
I started many years ago with a "for beginners" book, and didn't fully understand a lot of it by the end.
So I started trying to build something, and searched for answers to the things I couldn't figure out (and went back to the book numerous times). I don't think I ever finished that project, but by persisting through it, and figuring out how to solve the problems that I ran into, I learned how to build something, and it stuck.
Yeah. Building something and solving your gaps yourself is much better for learning than following a walkthrough.
A walkthrough can be effective onboarding if you're already familiar with the concepts. Otherwise, it takes the right kind of learning mindset to effectively take away results; not just following along, but internalizing the concepts and constructs.
For beginners, both the language and the concepts are new. Repetition/Multiple occasions help with internalizing.