This is called “the illusion of competence” coined by Barbara Oakley in “A Mind for Numbers” which is a book about learning math and other hard topics.
I never heard of Fireship until now. Most of the time I read the docs. I also write my own blog posts and notes for myself and link to docs on the web for when I run into issues. Not only is this beneficial for my future self, but also for others who may have run into this issue for the billionth time.
This video is one of the best I have seen so far. When I was learning to code, I faced many difficulties in the beginning because I believed that people who build things on live streams or RUclips videos, such as "how to code a responsive website" or "let's build a store," were doing so without any references and had an innate ability to code. However, after building many things, I realized that everything you create will be useful for future projects, but each new project will require a discovery phase, and you may need to spend a significant amount of time figuring out how to make small components of your site or application work. You will only understand how to use something in the future once you've used it before. This is valuable information.
Two tips: #1 ctrl + f to search for specific keywords. #2 tts text to speech for people with dyslexia or attention struggles can help to get audiofeedback simmultainiously as visual to reinforce the information. #3 Bonus tip, taking notes while reading it, even if you delete your notes can also add another layer of information reinforcement
One thing I’ll add. Coming from a self taught background. If you’re fairly new to programming, pick a couple of tools, JS/Python, Svelte/Django, Polars/Pandas, Postgres/MySQL/DuckDb/Sqlite and REALLY read as much of the docs as possible. Go start to finish and only skim through the bits you have high familiarity with. Learning to learn is hard and it’s only made harder if you regularly skip over the things you don’t yet know.
Great video! I went to a coding boot camp and we all despised reading documentation at first. Now that I'm several years in my career, documentation is much easier to read and understand.
This makes sense. im looking for material to teach me how to build my logical thinking and breaking down problems into smaller pieces before i get into implementation with a programming language. Does anyone have recommendations?
Awesome video dude. I was really struggling on how to learn to code and I also think that the better way is going through the documentation and trial and error. There's no magic!
This!!! At one point in time many moons ago I worked dev support. 80% of the calls could be answered by reading the documentation and the extensive knowledge base.
i started off only watching videos (now i use them only for high level understanding) but that’s very time consuming (even on 1.5-2x). There won’t always be a video on what you need, and sometimes the docs are obscure af for my particular use case. Sometimes you might even need to go into the actual source code. Also i didn’t realize how spoiled i was using JS (frontend) documentation. Some backend docs, you’re lucky if they even bother putting css on the page 😂
I am a coder and run my own software company but from time to time I do check videos from different channels on youtube to see what's new or to get basic information about some tool or framework that i have used. But I tell you that fireship is not one of the better options & I feel his purpose is not to teach rather showcase his knowledge so he can bring traffic to his paid courses which in itself is not wrong but at least one should cover all the basic steps. Initially i liked that it covered a lot in short period of time and even suggested his channel to many newbies and junior developers but i got a negative feedback from all that they practically didn't learn anything.
Speechify has been a huge help for me to get through docs. It’s a screen reader and almost turns docs into a podcast. Give it a shot if you aren’t a big reader :)
Could one of you document proficient people make a tutorial on how to read the docs? I mean basic examples of how to navigate and test commands as a new user would.
The problem with alot of docs is they are written by people who already know the thing writing it as a reference for the perspective of someone who already knows the things and just needs a reminder. And portability issues good grief; the lack of offline/pdf versions is a constant drain not just mentally but techwise +5MB doc pages or high CPU is weird. Or needing a build process to have a useable local copy of the docs.
Ngl, you're right, but the documentation in the JS ecosystem is on average incredibly weak, even when it's comprehensive. Definitely a factor for me moving from java.
Just in case anyone's in any doubt, the last 3 docs I've looked at: Redux's docs are comprehensive, but a mess. Sequelize: much improved tbf, but only in the last year or so. Class-Variance-Authority: 250k weekly dls, with functionally no documentation at all (it's simply a list of code snippets)
Yeah I agree with that. There is are a lot more bad docs than good... One benefit of most things being open source in the JS world is you can go source code diving. That is obviously not ideal, but when I come across lack of documentation, I go direct to the source to figure things out.
This is called “the illusion of competence” coined by Barbara Oakley in “A Mind for Numbers” which is a book about learning math and other hard topics.
I never heard of Fireship until now. Most of the time I read the docs. I also write my own blog posts and notes for myself and link to docs on the web for when I run into issues. Not only is this beneficial for my future self, but also for others who may have run into this issue for the billionth time.
This video is one of the best I have seen so far. When I was learning to code, I faced many difficulties in the beginning because I believed that people who build things on live streams or RUclips videos, such as "how to code a responsive website" or "let's build a store," were doing so without any references and had an innate ability to code. However, after building many things, I realized that everything you create will be useful for future projects, but each new project will require a discovery phase, and you may need to spend a significant amount of time figuring out how to make small components of your site or application work. You will only understand how to use something in the future once you've used it before. This is valuable information.
Two tips: #1 ctrl + f to search for specific keywords. #2 tts text to speech for people with dyslexia or attention struggles can help to get audiofeedback simmultainiously as visual to reinforce the information. #3 Bonus tip, taking notes while reading it, even if you delete your notes can also add another layer of information reinforcement
One thing I’ll add. Coming from a self taught background. If you’re fairly new to programming, pick a couple of tools, JS/Python, Svelte/Django, Polars/Pandas, Postgres/MySQL/DuckDb/Sqlite and REALLY read as much of the docs as possible. Go start to finish and only skim through the bits you have high familiarity with.
Learning to learn is hard and it’s only made harder if you regularly skip over the things you don’t yet know.
Great video! I went to a coding boot camp and we all despised reading documentation at first. Now that I'm several years in my career, documentation is much easier to read and understand.
This makes sense. im looking for material to teach me how to build my logical thinking and breaking down problems into smaller pieces before i get into implementation with a programming language. Does anyone have recommendations?
This is deep. And so right!
omg is that the 1 million grid guy?
@@MontyBasics maaaaaaybe
Awesome video dude. I was really struggling on how to learn to code and I also think that the better way is going through the documentation and trial and error. There's no magic!
This!!! At one point in time many moons ago I worked dev support. 80% of the calls could be answered by reading the documentation and the extensive knowledge base.
I want to learn TS and also be more aware of docs. "Just read the documentation" was the push i needed TY
using a screen reader has really helped me tackle huge blobs of words on the screen lol
i started off only watching videos (now i use them only for high level understanding) but that’s very time consuming (even on 1.5-2x). There won’t always be a video on what you need, and sometimes the docs are obscure af for my particular use case. Sometimes you might even need to go into the actual source code. Also i didn’t realize how spoiled i was using JS (frontend) documentation. Some backend docs, you’re lucky if they even bother putting css on the page 😂
I am a coder and run my own software company but from time to time I do check videos from different channels on youtube to see what's new or to get basic information about some tool or framework that i have used. But I tell you that fireship is not one of the better options & I feel his purpose is not to teach rather showcase his knowledge so he can bring traffic to his paid courses which in itself is not wrong but at least one should cover all the basic steps. Initially i liked that it covered a lot in short period of time and even suggested his channel to many newbies and junior developers but i got a negative feedback from all that they practically didn't learn anything.
Get a TTS plugin for your browser. Sometimes it can just be a dread to read it. It can be easier if you a TTS plugin like Read Aloud or NaturalReader
Enjoying the real talk in this video!
Speechify has been a huge help for me to get through docs. It’s a screen reader and almost turns docs into a podcast. Give it a shot if you aren’t a big reader :)
I really thought it was a notification from fireship.
Love the thumbnail hahah. Just read the docs! come on
Could one of you document proficient people make a tutorial on how to read the docs? I mean basic examples of how to navigate and test commands as a new user would.
The problem with alot of docs is they are written by people who already know the thing writing it as a reference for the perspective of someone who already knows the things and just needs a reminder.
And portability issues good grief; the lack of offline/pdf versions is a constant drain not just mentally but techwise +5MB doc pages or high CPU is weird.
Or needing a build process to have a useable local copy of the docs.
@1:15 Never was a truer word said 👍
thanks man
Learning from text docs vs getting a COURSE videos which one is best?
If you are new to a language, you probably need both. But experienced programmers don't need a course, just the documentation.
when i don't understand the docs i just copy the code and it work, and if don't work change a little things and it work
Thanks!
Fireship was good now its just videos around what is hyped most.
I like fireship but I do like have to rewatch the same video ten times to actually learn what he is talking about
Yeah same.
he hasn't made a good video in several years. Now it's just some clickbait stuff and random memes that are not funny
@@danko95bgd He makes videos people wanna watch.
@@danko95bgd tell me you're not following the times without telling me you're not following the times
Ngl, you're right, but the documentation in the JS ecosystem is on average incredibly weak, even when it's comprehensive. Definitely a factor for me moving from java.
Just in case anyone's in any doubt, the last 3 docs I've looked at: Redux's docs are comprehensive, but a mess. Sequelize: much improved tbf, but only in the last year or so. Class-Variance-Authority: 250k weekly dls, with functionally no documentation at all (it's simply a list of code snippets)
Yeah I agree with that. There is are a lot more bad docs than good...
One benefit of most things being open source in the JS world is you can go source code diving. That is obviously not ideal, but when I come across lack of documentation, I go direct to the source to figure things out.
@@CodingGarden Yeah I've definitely been looking to make that jump too, but it's definitely a jump (esp coming from an oop background!)
> Just Read The Docs
>docs are unreadable and unpractical, and wrote like at least readed 200k pages of some architecture of my gpu
like like like
CJ you were one of the best teachers I had when you were in NY. To this day I still do the stretch and drink water!!! @andrewlopezcodes