Myself I consider Documentation still important. Very important. I hate learning things in this field of knowledge by trial and error, or just by the use of the mouse ... by serendipity.

I  just dream of the possibility to interview skilled -and sincere- personnel in front of a running machine: that would let me analyze a package probably in just 7 hours whereas it takes me at least 12 full days to read and the test the basic functions.  Lacking this chance, I always read the manual of the package I analyze from the first to the last printed page. You don't need to tell me that it's boring. But it's instructive, even when the manual does not properly describe what the software is able to do.

Manuals and online help vary to great degrees in this respect. Additionally, information can be scattered: FAQs, web pages of the publisher's site, tutorial, help, reference manual ... One solid authoritative source: what a dream. How often it is disorganized, overlapping, repetitive. Documentation is often the last thing publishers worry about. It should always be updated, it should be revised by two kinds of skilled personnel: computer people and more user-oriented people. This is not always the case.