To paraphrase a line from Blazin Saddles
Manual we don't need no stinking manual.
Manual we don't need no stinking manual.
Mel Brooks is always appropriate! As is Monty Python. If you can't find a Mel Brooks or a Monty Python quote for whatever situation you're in, you're not trying...To paraphrase a line from Blazin Saddles
Manual we don't need no stinking manual.
Free donuts and coffee at their expense..... 🍩 ☕"RTFM Interface" makes it sound technical. All they usually needed to do is "interface" with the bloody manual for two minutes, and they would have saved me four hours on the road and out of the shop...
Death Wish at a minimum (or Biohazard, or Devil Mountain - I'm serious about my caffeine... My psychiatrist tells me I need to reduce my caffeine intake. "To what - about LD50?")Free donuts and coffee at their expense..... 🍩 ☕
To write a good manual takes talent and skill, and most people who do this work lack either or both.You'd be surprised with how many don't RTFM.... Or not! 😚 I try to keep local copies of the "Easier to Read" manuals for both my HomePatrol-2 and SDS100, as they're excellent references. I'm surprised a printed copy of the Sentinel manual hasn't been made available at Zip Scanners, just like the other manuals....
Get me the information - I seem to have the ability to take abstruse subjects and reduce them to terms a layman can work with. I've taught plenty of difficult subjects.To write a good manual takes talent and skill, and most people who do this work lack either or both.
You need tech skills to understand the engineering, and programming. Engineers typically have this.
You also need writing skills - the ability to write in grammatically correct sentences, assemble a well-planned paragraph, and create a narrative that leads from the reader's place of not knowing, to understanding the issue. This also demands that the writer understands where the reader happens to be on the understanding scale, and what information needs to be presented, in what particular way, to transport the reader to knowing.
The problem is that most writers lack the technical chops to really understand what they are writing, and most engineers can't write worth a damn.
That leads to horrible tech documentation.
And since most companies look upon documentation as a cost and an afterthought, they rarely invest the resources and resolve to do a good job.
And when you have a scanner that is as sophisticated as an SDS, that puts users in a tough situation.
I've had a caffeine jones for years, I started drinking coffee when I was six. But, I've been self-medicating lately - caffeine is one of the few things that works on migraines for me, and I've had a migraine (post-traumatic) since mid-2006. Eighteen years is a little long, don't you think?Been there, done that! ;D I don't drink coffee, but my soda intake (and other similar beverages) are mostly caffeine-free. Had a horrible incident about 25 years ago that caused me to switch from cola to root beer or ginger ale. Never looked back!