Hello folks,
Ok, I am a little slow on responding <g> Forgive me on this.
A few things come to mind when I read through this.
1. People reading, but not responding.
2. FAQ and How it is going.
3. Bullet Proof Examples on FAQ.
Just a few of my opinions which may or maynot be correct.
#1. People Reading but not Responding.
Though I cannot speak for all, I will speak for myself. There are many times I have read, but not responded. The reasons are as follows:
1. I have not dealt specifically with that arena, and my response would not be appropriate to help solve the situation. I don't like the blind leading the blind. If I post, I want to make sure I have solid code that *they* can check out, or a solid Idea that I have worked with, and been successful in implementing.
If I know of some code that may spring a problem, then I will mention it. I may not have knowledge of the project, but I always look at the Code if possible.
I also do about 98 percent of my reading from work. Thus, when I am on this forum, I am at work. My work is Programming computers in C/C++, Accounting, and Networking. In actuallity PIC's are a "Hobby" for me. A enjoyable hobby in which I started out with Phillips EPROM Mico-chips and switched to PICS. Should I spend a lot of time on this forum??? Well, depends on how you look at it...It helps me keep in tune with Micro-chip programming, as well as my other programming. I cannot test anything here at work that deals with PICS, but I can surely do my best to help others with ideas... and code.
Then another reason why I may not answer, lies in the problem of me signing on to late, or not seeing the message until later. If Member XYZ has already said what my answer is, why should I waste that members time reading through 2 exact same answers? If they need a recap for clarity, then I will answer. But I am not going to answer just for a "Higher Count" or Seniority status <g>. (I seriously doubt if this happens here, but I couldn't find another excuse for myself for not answering). <chuckle> Thus, the Lurking count goes up, but the response does not!.
With this info, comparing the Lurking and answer counters probably does not reflect the true situation at all times...I am a optimous... I want to think that the counters don't reflect people being lazy most all of the time, but rather some folks may not have the knowledge, or their answer may be a similar answer that has already been posted.
#2. FAQ... I think it is EXCELLENT. The uploads are extremely good. I think the reason why FAQ is not LARGE, is based on the idea that some things are just plain to *easy*. One must assume a person has *some* knowledge of programming a PIC, (or at least using a programming language). There are many examples given in the Manual of PIC. And to cover the exact same thing in the Manual is rather fruitless?
Thus, one must wait until a question comes up that the manual is a little "unclear" on. Or maybe a question that is out of the ordinary, and isn't exactly covered in the manual or other places.
The FAQ must be EXACT and to the POINT. So that a user can see the Title and say "YES, this covers what I am talking about, nothing else". The very second the thread starts to drift away from the topic, the user is starting to waste their time reading through goop that should not be in the FAQ. When a user starts to do this, the FAQ will begin to fail. YOu may as well do a search through the entire forum for your answer.
I would not expect the FAQ to be LARGE. But quite the opposite. I would expect it to be small, and quite percise on things that people have problems with.
How many different ways do you write to a LCD with PBP?
How many ways do you do a AD covert?
How many ways do you use a comparator?
How many ways do you use a timer and its interupt?
All of these questions are easily answered. and may or maynot make it in the FAQ. (Probably should make it though).
It is the programming inbetween that stumps, or gets the best of us... (or at least me <g>). And this programming inbetween usually has no business in the FAQ. Its a individual problem on their project. Not something that comes up every day of the week.
#3 FAQ MUST BE BULLET PROOF. Ralph is correct. All examples must be compiled and tested. Step throughs should be a good solid foundation for troubleshooting. If *all* possible, the FAQ should cover *all* angles of the situation. Granted it may be difficult to know and remember all angles, but it is important to know that posted material will/should work as described. People rely upon the FAQ for working solutions, or possible ideas to their problems.
Ok folks... sorry about the delay.... you can come tear this kid up now!
Dwayne
Ability to Fly:
Hurling yourself towards the ground, and missing.
Engineers that Contribute to flying:
Both optimists and pessimists contribute to the society. The optimist invents the aeroplane, the pessimist the parachute
Pilots that are Flying:
Those who know their limitations, and respect the green side of the grass...
Bookmarks