Finding answers.
WHAT OFFICIAL DOCUMENTATION PROVIDES
Authoritative, current information The complete language and library reference Usually, a tutorial and guides
WHY TO PREFER IT
It is correct for the version you are using.
WHAT TO CHECK ALWAYS
Which version the documentation describes.
WHY
Behaviour changes, and following documentation for another version wastes time.
WHAT TO LEARN TO READ
Function signatures: what is required, what is optional, what is returned.
WHY
It answers most questions faster than searching.
WHAT ELSE DOCUMENTATION CONTAINS
Notes on behaviour in edge cases Deprecation notices Performance characteristics
WHAT PEOPLE MISS
Those notes, which frequently explain the exact confusion they have.
WHAT TO USE COMMUNITY ANSWERS FOR
Practical problems, and worked examples.
WHAT TO BE CAREFUL WITH
Answers written years ago for older versions Highly rated answers that are now wrong Solutions that work without explanation
WHAT TO ALWAYS CHECK
The date, and the version referenced.
WHAT TO DO WITH ANY SOLUTION
Understand it before using it.
