My day job involves enterprise development, usually lots of back-end stuff.
With things like Java and C# - there's a lot of really high quality community-authored documentation around.
One of the things that really annoyed me initially, coming to the Unity ecosystem, was that the majority of community tutorials for Unity seem to be video tutorials on Youtube or Vimeo, etc.
I generally found them annoying, too slow or just generally unwatchable - I was really scratching around to find more written tutorials and doco on Unity (was very happy to finding the written PDFs that came with the Unity tutorials like Penelope).
But I've gotta say - the NGUI video tutorials have really changed my thinking on this.
NGUI may focus on the KISS principle, but it's still fairly complex to wrap your head around at first.
I'm certain the video tutorials have gotten me up to speed much faster than a written tutorial would have. And written tutorials would only be good enough if you spent a LOT of time writing them (look at the written tutorial material from Unity; they're quite good, but you can tell they've put loads of effort in to it).
Don't get me wrong - I still think reference documentation is important. It's particularly frustrating when you're sure you remember the tutorial going over how to do something, but you can't remember where the relevant bit is in the 40-minute video. Maybe a good idea would be to put in links to specific timestamps in the tutorials for any references doco where you've also covered that component in the tutorial videos?
It's made me think that maybe at my work, we could do a better job of documenting some developer-side things with videos instead of thousands upon thousands of words.
@ArenMook:
Watching the tutorials, it seems like you just record it all in one go - but there is the odd bit of editing as well. Does it take a lot of time to put together the tutorials videos, with a bunch of editing and stuff - or is it as straightforward and watching the videos implies?