3 ms·
Hyperlinks and footnotes. I wish blog/tutorial content making use of various libraries or non-trivial language features would link to something providing more i
by Jtsummers 6y ago
Hyperlinks and footnotes. I wish blog/tutorial content making use of various libraries or non-trivial language features would link to something providing more information if it's available. Even a citation (see "The Go Programming Language" section 4.5) would be helpful.
I'm learning Go (relearning, I learned it when it first came out but never used it) and came across something like this:
type Record struct {
Name string `json:"name"`
}
My first thought was, "Why is there a reference to JSON here?", the reason became apparent in the next section (so the order of presentation was poor to begin with), but my second thought was, "The language/compiler understands JSON?" If, on the first instance of this form, there were a link, margin note, or footnote to an explanation then the novice (either a programming novice or a language novice) would be able to more effectively dive deeper into the material in a guided fashion.
This is what intermediate-to-advanced material can do to really help out, especially for people who want to see real world use-cases and for one reason or another don't want to or haven't fully gone through all the basic material (or just forgot parts of it).
- travisjungroth 6y agoBackfilling the dependencies is a graph traversal problem. An author can put work in and add references for everything and it will help a lot. The problem is as soon as those links are to something that doesn't follow this pattern (most things), the student will be in the same position.