-More documentation is not necessarily better documentation. Err
or on the side
+More documentation is not necessarily better documentation. Err on the side
It is an unfortunate fact that making documentation longer can be an impediment
The tone of the tutorial (and all the docs) needs to be respectful of the
reader's intelligence. Don't presume that the readers are stupid. Lay out the
relevant information, show motivating use cases, provide glossary links, and do
-our best to connect-the-dots, but don't talk down to them or waste their time.
+our best to connectthedots, but don't talk down to them or waste their time.
The tutorial is meant for newcomers, many of whom will be using the tutorial to
evaluate the language as a whole. The experience needs to be positive and not