DEV Community

Best way to learn a framework/language

Medea on March 09, 2023

People prefer learning a framework/language in different ways. For example, some people (like me) like reading the docs and then going straight in...
Collapse
 
raibtoffoletto profile image
Raí B. Toffoletto • Edited

That's totally personal I guess. I see a lot of people who love video lessons about a subject, but for me it doesn't work. I started learning code by reading books and magazines and typing out the lessons/projects so I do much better reading docs and tutorials and going make something small and simple from it.

For example...
Last year I used the starwars api to build a simple Flutter and then a React Native app. Before I used the Chinook database to build a SolidJS + dotnet core webapp. This year I had to build a pokedex using the pokeapi for a job interview using React and now I'm trying to rewrite it using asp.net mvc integrated with vite+ts+webcomponents.

So my advice is keep it learning no matter what and find the method that works for you!! There's no write right answer here 😁

Collapse
 
vulcanwm profile image
Medea

great advice!

Collapse
 
oddward profile image
Mugtaba G

I generally don't like watching videos for tutorials, especially coding, I just find the UX of trying to read the small text + regularly pausing to keep up + it being harder to go back and forth to specific details very unintuitive for programming. I do however sometimes look at a general intro course or quickstart video, ones focused on the main concepts and bootstrapping etc.

I like written content for programming as it's quick to look through and see if it's what you need and you can follow at your own pace or easily save it or jump to specific sections. When I do follow a tutorial, I rarely ever follow it exactly, I kind of follow the main steps but change the content to suit what I need, and if something doesn't work as a result I start researching that specific problem and coming across other tips. I can't say yet if my methods are particularly effective for me or not lol, but it keeps me going.

Usual flow:

  1. Decide what kind of app I want to make (usually the inspiration to learn a specific tech, and usually something I'd actually want to use)
  2. Research the diff options of tech or approaches available 3.1 New framework that's useful for me? Look at an intro course on yt for main concepts, then a quickstart guide 3.2 Smaller tech that I can add to any project? Look at the docs or some blog post talking about it
  3. Optional: guides for installation, bootstrapping, templates etc
  4. After that, it's mainly the docs and searching specific queries about the problem I'm facing

Lately, one of the most useful new things has been joining the discord server of specific tech communities like React or Vue server, which usually has channels for getting quick help & discussions from passionate volunteers/members. And creator communities like Codu community. They're usually linked in the docs if available.

Collapse
 
krlz profile image
krlz

didnt know about codu, thanks for sharing!

Collapse
 
vulcanwm profile image
Medea

great advice, thanks!

Collapse
 
__masashi__ profile image
Masashi

In short, see tutorials and examples and then, create projects and .... actually WRITE code (Copy-Paste teaches nothing).
Repeat this and a person will get a firm grip.

let rec learn resource =
  if satisfied <> true then learn get_resource
  else take_rest
Enter fullscreen mode Exit fullscreen mode
Collapse
 
vulcanwm profile image
Medea

yea

Collapse
 
smsp profile image
Sobhan Mowlaei

In some framework and language, the document is not very useful in any project, and it gives us extra information, sometimes there is some tricks and unwritten document in a framework or language which we can learn from tutorials and pros

Collapse
 
vulcanwm profile image
Medea

that’s true

Collapse
 
krlz profile image
krlz • Edited

Hi there, well some tips here

  1. Choose a framework that suits your intended use case.
  2. Research the most popular frameworks in your area of interest and compare their benefits and drawbacks.
  3. Evaluate the framework's fit for your project's needs, its ease of use, the quality of its documentation, community support, maintenance, and user base.
  4. Avoid choosing a framework solely because it's currently trending.
  5. Don't hesitate to seek help from online communities, meetups, and other resources when you encounter difficulties.
  6. Enjoy the learning process and use the framework to build something cool.
  7. Avoid getting sidetracked by shiny new frameworks and stick to the one that meets your project's requirements.

Docs are a core part, but sometimes to learn a framework a domain knowledge can be a great and enriching experience, consider checking out books by authors such as Eric Freeman and Elisabeth Robson (Head First series), Brad Traversy (React, Node.js), Andrew Hunt and David Thomas (The Pragmatic Programmer), and Kyle Simpson (You Don't Know JS), they have a great experience not just in working with frameworks but in solving problems with them.

Collapse
 
vulcanwm profile image
Medea

great tips!

Collapse
 
sonicx180 profile image
sonicx180

I do no.2 but am going to try to do no.1

Collapse
 
vulcanwm profile image
Medea

nice!