> I am guilty of asking dumb questions.
> It happens most often when I am simply overwhelmed by
> whatever puzzle I am
> trying to work out. I try to limit the worst of them but
> sometimes the root
> of the problem is that I don't know enough yet to properly form the
> question. This especially true when my searches yield many
> too many leads to
> pursue.

IMHO the most important class of dumb questions is the ones that can not
be answered because the question is not complete. This includes 'which
chip should I use' without stating the intended purpose and numebr of
units, 'which compiler should I use' (which is almost un-answereable
even given enough side informations, 'waht is the best programmer'
without stating your personal time/money ratio and some other boundary
conditions (intended targets, DIY or build, ZIF or ICSP, etc).

I think such questions should and can be avoided, or rather: should be
augmented with the needed information so a relevant answer can be given.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics