I work in a technical industry, and I have read and written a lot of procedures and I believe in the importance of written procedures and manuals. Because of that I believe that the easiest way to learn is by recieving interpersoal training. Anyone that refuses to read manuals, recieve instructions or resists recieving help is dooming themselves to a hard time learning. The two Canon guides I suggested, are both well written, the printing is larger and easier to read, there are better illustrations, and the information is more in depth. I have read the Canon's manuals, they are good, but not the be all end all of manuals. The field guides go a step further then the canon manual. -rick
Luckless wrote in post #15105747
No clue. I've spent my life around engineering and computer systems, so reaching for the manual and documentation is just something that feels natural to me. I always find time to skim through them to hit the key notes, but generally I feel it is a failure on the developer's part
if I have to keep reaching for the manual for stuff. (Looking up details in docs is different. I can't remember all the parameter options on hundreds of functions across a few dozen libraries.)
And frankly, writing really good manuals is a hard task. I should know, I've co-written several manuals in the last few years. For military weapons systems... Several armed forces kept sending back our proposal and manuals because parts were 'too confusing', such as the power up sequence. Which is written on the units.