I feel striving for high quality tutorials and not simply accepting garbled examples for the sake of quantity is incredibly brilliant; I search, read, and practice many tutorials on other sites-- Flash, OpenGL, SDL, Ruby, CSS, etc: they are, for the most part, very poorly-written, inept, and often leave me more confused than when I began. To write tutorials one must be able to write and excel at technical writing, provide deep and concise explanations, diagrams (preferably), and an overall sense of continuity.

Daniweb will profit highly from implementing this new route in regards to tutorials. More programmers will learn more- word will spread- more new members will join- things will grow exponetially.

Thanks for your work, HappyGeek and Dani. Quality.

Matty

Thanks a lot guys. This is a very object oriented community which makes me a proud member of it. I also believe in quality and sincerely hope that some one will write some basic tutorials on open source areas soon. I am starving for some really good knowledge and looking forward to it. God bless all. Cheers.

Maybe you guys should create a thread to post the "exact kind of tutorials" you require (language, a particular concept etc.) so that if someone already has enough knowledge on that topic, he would consider writing a tutorial whenever he has got the time.

Sounds like a good idea, except I think there are several reasons why we don't do this. Not everyone is a good writer. There are plenty of people who are very knowledgeable about a particular topic, yet would be very bad at writing a tutorial about it. No sticky will be able to change that.

That's why it's invite-only, and I guess if we as Staff Writers see someone posting who has talent, Davey or Dani will send them the link. I agree that there are little things that would help, but such things would be merely tweaks and would get snipped out in the editing process.

Another problem about such a sticky would be that it would "encourage" regular non-writers to send their half-assed attempts at writing them to Davey, and then he would have even more work than the little that would be saved from such a thread.

Not everyone bothers writing tutorials, in fact, if they are not proficient, many people shirk away from it. And adding a disclaimer like "All half assed attempts would be rejected" should get the message across quickly. After all this, the ones who remain are the ones who really can write something good and worth reading.

>in fact, if they are not proficient, many people shirk away from it.
Then how come Davey had to clean up the tutorial section?

>adding a disclaimer like "All half assed attempts would be rejected" should get the message across quickly.
Perhaps I should rephrase my previous statement. What I mean is that it's likely to attract people who are somewhat good at writing tutorials, but simply do not match up to the DaniWeb standards.

The truth is that many people think that they can write a tutorial, many people think that they can simply steal a tutorial from somewhere else and change a few words, many people decide to 'have a go' without giving it any real thought beforehand.

Every one of these submissions had to be checked, consuming a lot of time, under the old system. Anyone could post a tutorial, and the numbers stacked up quite quickly in the moderation queue.

By making it harder to submit a tutorial, the hope is that by some strange twist of irony we will get fewer but much higher quality submissions. Not least because by the time the member gets to the 'writing it' stage, we will have agreed on the content and the style and know in advance that they are up to the challenge.

I never said that the way tutorials were submitted be changed, its good the way it is now.

But having a thread where we could pool up tutorial requests would interest those people who are proficient in writing tutorials and they could consider writing tutorials on the popularity of a particular topic in the thread say for eg C++ memory management techniques or how to avoid memory leaks.