-
Start with an ambitious project
-
Get stuck
-
Curse everything about said language or framework, “why did they do it like this”
-
Read the docs and find out why they did it like this
-
Feel stupid
-
Finish the project (or at least the part you actually cared about) with your new knowledge
-
Feel smart
-
Repeat until you know said language or framework
How do you approach learning a new programming language or framework?
Submitted 10 months ago by d_2@programming.dev to programming@programming.dev
Comments
gerryflap@feddit.nl 10 months ago
kryllic@programming.dev 10 months ago
Easy to get caught in a perpetual loop with steps 4 and 5
MaoZedongers@lemmy.today 10 months ago
You should be learning a bit more with each loop though.
Even banging your head on the wall against something eventually gets you somewhere.
nitefox@sh.itjust.works [bot] 10 months ago
I get stuck at step 2
starman@programming.dev 10 months ago
- Read the documentation
- Try some simple examples from the docs
- Build a simple project
Solemarc@lemmy.world 10 months ago
Either I come up with a new project or I rewrite an old project in the new language.
I used to do those old school language tutorials where we start with how to write a variable, then how to write a function, etc. but I think that’s better for complete beginners just starting out.
rutrum@lm.paradisus.day 10 months ago
I’ve done project rewrites. This minimizes the problem solving to mostly just syntax, sometimes a new paradigm if the framework is different enough. But in my experience a rewrites goes so much faster than I expect it, since theres a very clear goal to achieve while rewriting. If someone has an existing project to rewrite, I recommend it. If not, you could implement some project in a framework your comfortable with, and then do a rewrite in the new thing.
puffy@lemmy.ml 10 months ago
Read. Build. Repeat.
muhanga@programming.dev 10 months ago
Is it possible to build XML parser in it?
If answer is yes then i will build XML parser in it.
Solving a problem you know how to solve and solved more than once is a my goto approach in learning languge or frameworks. Translation of already solved problem to the new operational model or semantic exposes a lot internal stuff and marketing double talk.
This is a lot of work and time so can not recommend it for all cases and situations.
abhibeckert@lemmy.world 10 months ago
Lately I use ChatGPT 4, with a long running conversation where I explain what I’m trying to do, what tools I’m using, paste in sections of code that I don’t understand, asking what changes I should make, give it error messages I’m seeing, etc.
moreeni@lemm.ee 10 months ago
Get theory from somewhere on the Internet (videos, tutorials etc.), then do exercises on platforms like Exercism. Once you feel like you are getting good at it, start replacing the time for exercises on time with real projects
PoY@lemmygrad.ml 10 months ago
i like to douse myself in mud, then slowly creep up on it from behind, taking extra care not to break any twigs or ruffle any leaves, then I grab it and hold on for the ride of my life
MaoZedongers@lemmy.today 10 months ago
Rewrite one of my old C projects in it and compare the difficulty, ease of understanding the code, any issues/boons in documenting it, etc.
AMDmi3@lemmy.world 10 months ago
Read official docs, then rewrite some small own project in it.
kogasa@programming.dev 10 months ago
Start a project with a good template and learn by tinkering. Some languages/frameworks have some canonical starter templates (.NET, Phoenix) and most others you can find by googling “x boilerplate.”
JakenVeina@lemm.ee 10 months ago
Build something that already exists. My go-to is usually dir.exe.
Mad_Punda@feddit.de 10 months ago
Solve advent of code in it
nathanjent@programming.dev 10 months ago
Good for programming languages. Not always applicable for frameworks.
small44@lemmy.world 10 months ago
- Watch a project tutorial video
- Code along with the video and taking notes
- Create my own project with the notes i took and documentation
Lmaydev@programming.dev 10 months ago
I’ve started using LLMs for this. You can get up and running incredibly fast this way.
I use enterprise bing at work so it sources each sentence so I can go directly to the docs if I need to.
I’ve found it really superior to reading docs as it’s interactive. Being able to ask follow up questions is very powerful.
I’ve noticed the new batch of juniors at work are able to get productive very fast by using them.
owsei@programming.dev 10 months ago
rebuild stuff
I’ve remade a temperature converter cli 3 times in rust. Just to understand enums, structs and the borrow checker. Then I made an http server, that acted as a library’s book borrowing system.
anti_antidote@lemmy.zip 10 months ago
Honestly I just open up a new project and start fucking around until I figure out syntax, language features, and how files relate to each other