Why,would,read,about,when,coul computer Why would I read about it when I could be doing it instead&a
----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc
I spend about 10 hours a day reading and have yet to read asoftware manual for any of the 50 apps I have on my computer.They don't make sense to me and they insist on putting toomuch stupid stuff in there like disclaimers and marketinghyperbole. What good is that after you've already boughtthe software?Personally, I read the more sensible "Quick Start" guidesand then only skim those to get the key points. The way Iuse the software is usually different than that envisionedby the designers and even other users, so it really onlymakes sense to look up stuff when troubleshooting.If I read the manual for my digital watch, my cell phone,my two-line digital cordless phone, my PDA, my printer andmy ebook, I'd never use them for lack of time. What do Ineed to know more about my software for if it is servingit's purpose? What I need is for everything to be a hostedapp on the web and universally accessible wirelessly withbuilt-in voice recognition troubleshooting software.That way I could just say "Diagnose error" and it wouldfix itself. I don't care HOW it works, just THAT it work.If it isn't relevant to me, it isn't relevant.Why do you think the trend is toward sytsem on a chip (SoC)?Have you ever read the owners manual for your car? If youhave. Did you learn anything? Did it make you a betterdriver? No need to read marketing hyperbole or disclaimers,I just want it to work. When it breaks, I don't want tolearn why, just fix it please. I won't buy another one ofthose because it breaks too often.I think only help-desk personnel, who would rather behacking the Pentagon and technical writers are upset thatthey aren't writing best selling novels. They don't getpaid as well for hacking and nobody reads the work oftechnical tomes of the unfulfilled writers. At least theyare both being paid to do something.In the early days of photography only scientists could bephotographers because they needed to know how to obtainand mix the chemistry, apply the emulsion to glass plates,develop those plates and do that entire process again whentransferring negative image the to paper. Are we any lesswell-off now that cameras are disposable and we can seeour film in an hour without going into a dark room even once to do it?My wife is ready to throw away her new $1000 computerbecause it won't accept the password when logging on tothe ISP. There is a real disconnect between the problemsand the source here. That is usually the case when thingsget so complex. Reading manuals won't help.I look forward to the day when the software designersrealize that the users don't care how they created thatamazing software and that as long as it will do what theybought it for without fuss, it will be popular and well-liked by the buying public. If it takes a day of reading,I'll go buy something that works without study instead.Is your VCR clock still blinking? If not, I bet you stillend up seeing the "blue screen of death" as often as I do.
Why,would,read,about,when,coul