00:00 Learn how to properly read documentation 02:10 Reading documentation is important for programmers 04:19 Navigating documentation is easier when you understand its structure 06:32 Documentation is for getting started or looking up specific functions 08:35 Using documentation to understand default values and parameters 10:42 Finding documentation for Python packages 12:53 To understand code, go to the documentation and source code 14:56 Reading documentation: Getting started, User guide, and API reference
Sorry man, this was not helpful. I was hopping this video was going to help me understand how to decode what the document was talking about. like with the python print example. what are all the other option/parameters? how do determine if they are required or optional? So I get overwhelmed by the docs and then don't read them.
at that point your problem isn't not knowing how to read documentation, its just not knowing python syntax in the first place. you need to take a step back and fill in gaps in your knowledge about the fundamentals
I come from a Java background and the documentation is written in a way that makes it super easy to understand. I can't get to grips with the Python documentation either and have exactly the same problem as you - how am I supposed to read it all, all the parameters, what is mandatory and what is not. These docs are terrible^^
@@sebbyteh9203 Yes exactly. And agreeing with the others, I know how Javadoc looks and after that, I conclude that the Python documentation is a terrible cobweb of unordered information that screams _"I beg you to waste lifetime reading me like a book"_
Problems with documentation, you need to know the function to search for it. When you have logical problem or something where you don't know the way, the documentation will not help. Because you can't ask like "How i do ..."
in theory thats where the user guide /getting started style docs come in, the people making the library being documented should explain the normal use cases for what you would typically be doing and whats possible, and then you fill in the gaps and go from there using the reference. again, thats only in theory sadly lol
Thank you for this! I felt pretty dumb searching for a 'how to read instructions' video hahaha. I didn't know about the CTRL+click on the package name to get the source code thing, so thanks for that as well.
Read the documentation from top to bottom isn't useful. I think is important to understand what the tech is, what it supposed to solve , who need it and why. Try a basic use and then go straight to what your current problem needs from that documentation.
too much talkative without any real matter up to 8 minutes. for reading doc, need to understand the meaning of symbol enclosed text, identify mandatory and optional part and others things, which i don't know thus watched your video to know but disappointed totally
freaking lame Video....people clidked on your video thinking you would be explaining things like ~breakpoint(*args, **kws)~ all the key words or at least the most important ones like kws, args and what they mean or what people can pass through them. you explained to people how to read a book. congrats to all of us!
00:00 Learn how to properly read documentation
02:10 Reading documentation is important for programmers
04:19 Navigating documentation is easier when you understand its structure
06:32 Documentation is for getting started or looking up specific functions
08:35 Using documentation to understand default values and parameters
10:42 Finding documentation for Python packages
12:53 To understand code, go to the documentation and source code
14:56 Reading documentation: Getting started, User guide, and API reference
Sorry man, this was not helpful. I was hopping this video was going to help me understand how to decode what the document was talking about. like with the python print example. what are all the other option/parameters? how do determine if they are required or optional? So I get overwhelmed by the docs and then don't read them.
Damn, what a great feedback while being nice when disagreeing!
I'm sure you'll get there and would find your answers! Have a nice day 😊
at that point your problem isn't not knowing how to read documentation, its just not knowing python syntax in the first place. you need to take a step back and fill in gaps in your knowledge about the fundamentals
I come from a Java background and the documentation is written in a way that makes it super easy to understand.
I can't get to grips with the Python documentation either and have exactly the same problem as you - how am I supposed to read it all, all the parameters, what is mandatory and what is not. These docs are terrible^^
Documentation is like a handbook/dictionary, you don't read them, you use them by referring them when you need it
@@sebbyteh9203 Yes exactly. And agreeing with the others, I know how Javadoc looks and after that, I conclude that the Python documentation is a terrible cobweb of unordered information that screams _"I beg you to waste lifetime reading me like a book"_
Yessss! I was looking exactly for that a few days ago! That's a meta skill! Thanks!
Problems with documentation, you need to know the function to search for it. When you have logical problem or something where you don't know the way, the documentation will not help. Because you can't ask like "How i do ..."
One solution is to create a T-shaped understanding of the entire documentation.
@@nasim3987 elaborate? I think I understand a little
in theory thats where the user guide /getting started style docs come in, the people making the library being documented should explain the normal use cases for what you would typically be doing and whats possible, and then you fill in the gaps and go from there using the reference. again, thats only in theory sadly lol
well now, u can ask LLMs for that !!
One more video about how to write documentation :-)
copy a doc like pandas'doc and modify it directly
Thank you for this! I felt pretty dumb searching for a 'how to read instructions' video hahaha. I didn't know about the CTRL+click on the package name to get the source code thing, so thanks for that as well.
Stackoverflow is old news i find myself using chatgpt often :)
what if I want you study from scratch using only the documentation?
This was very helpful! Thank you for putting this video together for us.
Glad to hear you like it!
thanks for the video
you should have also explained how to look up for *args and **kwargs parent class
Good video idea. Stack overflow mods approve!
I am a beginner...I am in love with the PHP documentation
Sounds a bit greek myth to me
ChatGPT also useful for more common libraries but it only records updates up until September 2021
Couldn't it be useful if you just copy paste all the docs and ask him questions about them? Then he doesn't have to refer to them by Sept 21 memory.
@@philipe1502 Just copy and paste the link for the specific page that you want to know about documentation. Then, he will give you "updated" answers.
Ah. So Phind should also be able to help me with this as well.
it is often much faster and on point to ask AI. The trick is the question should be rather on basics
Thanks Mr. Victor Krum
aye I liked the video of a tutorial on how to make a tutorial, this is valid
Thanks brother, I needed this!
You don't even know how much you helped me, thanks!
thank you i didnot know this.
Very informative
Thank you kind sir
2:20 start video
Eid mobarak
Thanks For Making Video On this Topic
I searched for this
Heck i think all of python help menus looks like gibberish to me if being honest.
It funny because people said "RTFM" when we literally can't read the manual😂😂😂
Thanks.
Read the documentation from top to bottom isn't useful. I think is important to understand what the tech is, what it supposed to solve , who need it and why. Try a basic use and then go straight to what your current problem needs from that documentation.
fyi "RTFM" full form is "read the fucking manual"
too much talkative without any real matter up to 8 minutes. for reading doc, need to understand the meaning of symbol enclosed text, identify mandatory and optional part and others things, which i don't know thus watched your video to know but disappointed totally
Thats what i want know
oh great
freaking lame Video....people clidked on your video thinking you would be explaining things like ~breakpoint(*args, **kws)~ all the key words or at least the most important ones like kws, args and what they mean or what people can pass through them. you explained to people how to read a book. congrats to all of us!
So tired of people uploading videos and not explain what the title says they are going to explain.
😂 if you need to be pro atleast read docs everyday for 1hr.
bro all the 2 minute talk was unnecessary, we came here to learn to how do it so just go straight to the point