C# documentation worth bookmarking
Good documentation answers a question in seconds. The skill is knowing which page to open and which to ignore while you are still learning.
Keep these close
- The language reference, for the exact name and behaviour of a keyword.
- The standard library reference, for the methods on the types you use daily.
- A search engine, for the error message you just received.
How to read reference material
Read the signature and the first sentence. That is usually the answer. The long remarks section matters when the behaviour surprises you, not before.
Do not read it front to back. Documentation is a lookup table, not a course. The lessons here are the course. The reference shelf gathers the pages worth keeping.
With a bookmark or two in place, start writing code in the data types lesson.