Knowing how to use documentation is probably 80% of what helps me write my apps. That's the truth. The improvement of my code has come with the improvement of my ability to navigate the documentation.
In many cases, it's helpful to see some example code or to just be told the answer, but it's in my interest, the asker's interest, and in the interest of everybody who frequents this forum that we know how to look to the documentation.
I've seen a lot of people bash new developers for not looking at the documentation, and that sucks. Nonetheless, it's TRUE that being able to read and navigate the docs is an ESSENTIAL skill, and in this case that seemed to be the root of the user's problem.
Maybe we need to come up with a documentation guide. Some meta-documentation? Some tutorial creators like Nitrex88 do a great job of emphasizing the documentation rather than just pulling code out of a hat.
Cheers,
charlie
|
