Perfect, that's how I approach any new body of technical knowledge, i.e. 'How does this help me solve a problem or accomplish some task?' It's harder when I have to wade through tons of seemingly irrelevant stuff to get to something that answers that question. At my age and situation (starting a new business), I don't have the luxury of time to learn a new programming system (no matter how easy it is) unless I can see a direct (and immediate) correlation to something that will make my life or workflow easier.
Rob.......... On Saturday, January 30, 2016 at 5:01:18 PM UTC-5, Edward K. Ream wrote: > > Leo's tutorial, reference and cheat sheet have been thinly disguised > encyclopedias. Very dry. Soporific. > > Contrast this with the Code Academy. The "lectures" deal with solving > real problems. Shorter code, more useful. Exciting, maybe. > > This would be a good model for a rewritten tutorial. > > People have talked about task-oriented documentation in the past, but I > haven't understood what they meant until now. > > This isn't really about telling stories that "stick". It's about solving > important problems. Now *that's* something that has a chance of getting > people involved. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
