Something else you wrote about documentation I found very good ...
Mark S.
TW technology is more like learning a human language than a programming
language -- there's a handful of rules and then a whole lot of
exceptions.
It strikes me that thinking into the various types of "exceptions" and explaining them first could be a godsend.
For
instance, I find that quite often something does not work as I expect NOT
because I got the "code" wrong so much as that I got the layout wrong
in some way that I wasn't clear about. "Blank lines" in TW and how they
work still often catches me out.
One thing that people who have
more experience than me have is "Implicit Knowledge of Exceptions" and "quirks you need to grasp". I think Explicating those
could be immensely useful. In exactly the same way as, for instance, in
teaching English, you use can use exceptions to highlight more regular rules.