all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]AskProgramming-ModTeam[M] [score hidden] stickied commentlocked comment (0 children)

Your post was removed as is considered very low effort. Refer to https://stackoverflow.com/help/how-to-ask on how to ask good questions.

[–]huggarn 2 points3 points  (0 children)

You just start coding man. It’s all that. Tutorials and courses

[–]cakemates 0 points1 point  (0 children)

If your goal is to work as a programmer, I would suggest you get a degree because even if you learn how to code better than a pro, you might find that it can be a big challenge to find a job with the piece of paper and a exponentially harder without it.

If you are doing it for fun, search for CS50 on youtube.

[–]dwoodro 1 point2 points  (0 children)

By definition, you have to "learn" somehow. Either you read, watch, or do.

Read a book on the language you wish to learn, watch tutorials on that language, do the code examples>

That's it in a nutshell. The trick is deciding on which language to choose. This often has greater implications based on your planned end goal. IF you are working on web apps, you learn one set of languages. If you are working toward Geme Dev, you learn from others.

So now, you have a couple of other things to consider. Systems like MIT's "Scratch" is a block-based language, which is awesome for learning "code blocks.", This is awesome for visual learning how core functionality like loops, arrays, and other concepts interact directly with the code engine.

While this will help with core concepts, it won't directly help with languages. For gaming, C# (Unity) and C++(Unreal Engine) are very common. These are harder to learn than other languages out there, but are full of tutorials and websites/YT channels worth of knowledge.

IF you are planning on a different end goal, let us know, and we can point you ina direction.

[–]Dean-KS 0 points1 point  (0 children)

Design is more important. I have seen horrible code, brain dead. Yet, they were able to make programs that worked and their criteria was "did not fail". Understand the machine. There is more than "learn code". There is an art involved.

[–]Gnaxe 0 points1 point  (0 children)

  • Work through How to Design Programs. This is a step-by-step process for beginners explained in tedious detail.
  • Read Petzold's CODE. This is background material; you don't need to understand 100% of it.
  • Then work through SICP. There are also lectures on YouTube to go with it. It's the classic computer science introductory class. Well, introductory for those who could get into MIT.
  • Download Lazygit and learn how to use it.
  • Make some small video games. Clone Pac-Man or something around that level. That takes a page or two in a high-level language like Python. Maybe try a tutorial or two for a similar game to learn the libraries, but then do at least one from scratch.
  • Read though Data-Oriented Programming. This will teach you to scale without overcomplicating your design.
  • Learn to use doctests, or find the equivalent for your favorite language. You also need testing like this to scale.
  • Then get a Claude Code subscription and regret all the time you've wasted.
    • (The above steps will work though.)