Magazines (PC World, Wired, etc.)
9% (4 votes)
Books (O’Reilly, MaintainIT Cookbooks, etc.)
7% (3 votes)
Conferences
9% (4 votes)
Websites and blogs
41% (18 votes)
Listservs and discussion boards
0% (0 votes)
Trial and error (aka breaking stuff)
20% (9 votes)
Co-workers
2% (1 vote)
Classroom training
11% (5 votes)
Total votes: 44




learning about technology and software
When it comes to new software, I always avoid the user manuals, How-To books and resources, and other such tools until after I've grabbed the software (or whatever the technology is, such as a handheld device, etc.), installed it, and fired it up.
I use stuff to learn about it. I was to see how solid it is. In all my years of using computers and other tech toys (going back to 1978), I've never read a manual prior to using anything. Only one piece of software was so un-intuitive that I had to refer to the manual to figure out how to do anything with it! Yes, despite having to turn to the manual to even begin using the software, I did give it a fair trial, and in the end, no, it wasn't adopted.
A well-developed piece of software or other technological gizmo, whether a handheld device (phone, tablet, etc.), or anything else, should be designed so it's user-friendly. Basically, if it isn't intuitive, the design is all wrong.