Additionally, we could have a page of various problem threads in the wiki - something more extensive than the FAQ, but just a simple list of threads from the OS Development forum that were about obscure problems but actually went somewhere, perhaps in a table with a better-stated problem description.
Just my 2 cents.
That won't work. I don't know if anyone else has picked up on it, but perhaps the reason WHY the newcomers keep posting up distasteful questions is because they come around with the wrong level of preparedness
. And of course, added to that is the obvious misunderestimation of how much they are supposed
to know for any given stage in development.
I don't know if anyone else has picked this up, but, a question such as:
"Hi everyone I'm from UK, and I like programming and computer and I learned some C in college, and want to grow on it, and I thouht I could make I own o.s. I have some great ideas, and I think i culd really get somwhere, but <here's the digression> unfortunetly when I tried compiling the source <error #1> frm the Bare Bone Wiki, it gave me an error.
It keep sayin "Error Unsupported file Format" <annoyance #1> and I tried evrtyhing but no avail and I now have major frustratin this so hard.
Plz help me if anyone can, I really appreciate it, thanks.
(Note that I didn't actually take that from anywhere. I simply typed it up while assuming the mindset of an underappreciative, non-investigative, reading-phobic individual, and inserted one or two patterns I picked up on from posts that are similar.)
The poster demonstrates a lack of initiative, and a reluctance to use Google. I don't know if it's just me, but after I first compiled the Bare Bones, I felt so stupid, I just threw it away and spent about two weeks re-reading it, and several other articles alongside repeatedly, and using Google intensively, such that I came back after that bit of reading and understood everything so well, I just re-wrote the code by myself.
Does it occur to the poster, maybe since this is only the beginning of his development, and he already has to face the fact that he is completely unprepared, that he is ill-equipped to handle the rest of the project, and therefore should wait, and just read a bit more, then try again?
And, question: does it strike the poster that...you don't NEED to get going RIGHT AWAY, but that small pauses in your dev momentum are completely okay, and everything doesn't have to be continuous? That you CAN take a pause to read for about two weeks, and then come back? So you don't need to post questions on the forum, since the information is right there? And if you read it you'll eventually understand?
And more importantly: that the fact the fact that YOU don't understand doesn't mean that something is wrong with "the system" or the way the article was written, but that YOU just aren't yet at the level necessary to come to grips with what's in the article? I believe people are so accustomed to having things watered down for them that they automatically assume that everything should be stepped down so that they can adjust.
See I don't chock the questions up to a lack of knowledge, (which, yes, does constitute a large part of it), , and definitely not to a lack of availability of information, but rather to a bad attitude.