New Language Roadmap

Recorded live on twitch, GET IN

MY MAIN YT CHANNEL: Has well edited engineering videos

Discord

[Cyber_Sandwich]

My roadmap to learning new language:
1) open Indian guy tutorial on it
2) practice
xD

[Wanderer]

This only works if you already know like 5 other languages, that’s all transferable. But if its your very first language this is not nearly sufficient enough

[mathijsfrank]

For me I always skip step 2. Id rather get started with coding as soon as possible and then read more documentation, when I feel a bit more comfortable or if I come across something i dont understand.

[captainfordo]

My roadmap:
Step 1: Learn C
Step 2: Stick with C

[MrElderwand]

I just hope this stays forever on Prime' channel. Please don't delete this

[Feenskee]

It's definitely better to spend more time on a project than reading all of the documentation or following a video tutorial

[DanielAlbanoIII]

What works for me is to find a super easy and interesting project tutorial on youtube, follow it step by step, and then try recreating it from scratch. It forces me to understand from my mistakes and helps me understand the documentation better. And then i try experimenting with the syntax to test if i really understood how it works. After that in the end it really comes down to practice practice practice...

[CottidaeSEA]

I do it in a similar way, but I don't learn nearly well enough by simply reading, so I have to continuously use the knowledge to a small extent in order for the information to really stick. Say I read about a specific class; I then need to use that in one way or another, even if it's just the bare minimum to kind of get a feel for how it's used.
I can read the documentation and see what methods exist, etc. but then I usually just go down a rabbit hole while forgetting why I even went into it in the first place, so I need the actual code example that I write for myself in order to process the information and to get a better picture of how things interact.

[Garfield_Minecraft]

I skipped everything and start a project without knowing anything, and learning things along the way
it only takes 2 days(not for learning the language I mean to setup the environment, and fixing errors, and stuffs)

[avichiii]

Python,
SQL,
C,
Bash,
Assembly,
Javascript,
HTML,
CSS.

After learning all of these I can finally agree with this type of suggestion.

[yurilsaps]

1) watch the 9h YouTube tutorial
2) go to sleep

[ddcde]

I love the comment at the end telling you to turn of copilot. I actually use copilot to learn new languages if they are not too recent (a.k.a the model was trained on sufficient existing data).
I add a lot of comments to my code to hepl copilot figure out what I'm doing and it will suggest things. When I come across something that I am not familiar with, I look it up to understand what it does.

For me, this method is like combining step 1 and 2 as copilot shows me the techniques of the language right of the bat because they are common patterns that it was trained on.

[Saru-Dono]

I do it similarly, but the first thing I try to do, to understand the basics and the syntax is sent an HTTP request. Usually I choose a free weather API, but honestly anything works. I find it a nice introduction to an unfamiliar environment and covers quite a lot of the ground rules in a language

[PeterMilko]

code in the same language every day for 10 years. Thats what i did. Now I can make a video game solo

[niteeshkumar]

Exactly this is what i think but what i like to do once i gotta understand the language syntax and after testing some crazy algorithms into it, i go for the projects people created on github to read the production kind of code

[MrLowbob]

I like the path
would love to see some more details on how you actually practically approach this (perhaps kind of in a video series?) because for me 1 to 3 are basically one point. I start reading the doc and explore the syntax along the way and when i think I have a basic Idea of how it works I start with code challenges/advent of code things/mini projects to explore further and read docu kind of on demand and inbetween.
and after that I start with actual project work, if I got something lined up.

[star-warsien]

I think starting a project is the best first step. In the process, you will learn the language, syntax, and techniques. It kind of forces you to if you are truly passionate about the project.

[turbojax]

I like finding a project I want to make in that language and then learning out how to make that program and solving problems along the way. Typically I make something that I already made in Java bc I know Java well.

[manofacertainrage]

As someone that augmented the documentation with newsgroups, man pages and books since searching sucked at that time (AltaVista & Lycos mostly), I added Safaribooks for about 10 years and then YouTube videos and courses (tutorials) with books only when deciding to do a deep dive. Like anything else, moderation is key - while a language with reasonable documentation can be learned, languages generally have associated systems and those could use some investigation before use - Erlang, Spring and CORBA come to mind. It's funny we have this discussion because C is the language of UNIX and many consider an OS class part of basic knowledge - and in a sense that OS class was a tutorial. Perhaps I'm mixing up a class, a course and a tutorial, but they blend together if you squint.

[baxstart]

ngl my roadmap to actually learn and practice a lot of a language's features is just to make my own interpreted language using it, cuz in that way you can learn the language's file handling, OOP, enums, hashmaps, loops, functions, switches, string handling, error handling, castings and more