3 ms·
If a (software) FAQ is well-written, I like to read them. They answer the problems I'm likely to find when I use the software, while providing interesting info
by rwmj 13y ago
If a (software) FAQ is well-written, I like to read them. They answer the problems I'm likely to find when I use the software, while providing interesting information on corner-cases.
Here are a few examples of good software FAQs which are entertaining to read in themselves:
http://ffmpeg.org/faq.html http://ffmpeg.org/faq.html
https://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/ https://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_...
http://libguestfs.org/guestfs-faq.1.html http://libguestfs.org/guestfs-faq.1.html (NB: I wrote this one)
- jseliger 13y agoIf a (software) FAQ is well-written, I like to read them. They answer the problems I'm likely to find when I use the software, while providing interesting information on corner-cases. Me too. I wonder if geeks (or their cousins "infovores") are more likely to read FAQs, and read them carefully, than the general public; if so, geeks might also be inclined to overestimate the importance of FAQs, or the willingness of non-geeks to read them.
- eterm 13y agoFAQs are a good fit for game manuals, where often layers of rules have strange interactions which make a FAQ to settle a few rule questions or "gotchas" important and interesting. But FAQs for a web application I think is a bad fit, it is generally more useful to have a forum (so you can get real feedback on what is frequently asked) where common questions will bubble to the top more often. Or if you're big enough, a stackexchange which handles genuinely frequently asked questions better still.
- jimmaswell 13y agoThe FAQ is supposed to be so people aren't wasting time on the forum asking the same question a million times. The project I'm on has a very useful FAQ with questions that got asked all the time when it wasn't there. It made them asked less, but people still don't read it sometimes.
- vog 13y agoAs a side note, the foreword of the SVN-Book gives a very good explanation why so many FAQs are bad, and why some of those aren't really FAQs at all: (http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.foreword http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.forewor...) | A bad [FAQ] sheet is one that is composed not of the questions people actually ask, but of the questions the FAQ's author wishes people would ask. Perhaps you've seen the type before: Q: How can I use Glorbosoft XYZ to maximize team productivity? A: Many of our customers want to know how they can maximize productivity through our patented office groupware innovations. The answer is simple. First, click on the File menu, scroll down to Increase Productivity, then… | The problem with such FAQs is that they are not, in a literal sense, FAQs at all. No one ever called the tech support line and asked, “How can we maximize productivity?” [...] [It's] a lot easier to make up imaginary [FAQs] than it is to discover the real ones. Compiling a true FAQ sheet requires a sustained, organized effort [...] It calls for the patient, observant attitude of a field naturalist. No grand hypothesizing, no visionary pronouncements here — open eyes and accurate note-taking are what's needed most.