As someone who writes a great deal of tutorials, and even just published his very first book just recently, this is an area I find a bit tricky.
It's not a matter of being qualified to write a tutorial, I wrote a C++ tutorial that has been incredibly well received, but I am by no means the greatest C++ programmer in the world. ( Far from it, I've been using higher level languages for most of the prior decade, so I certainly don't know the nitty gritty and can get absolutely schooled on the subject by some of the posters on this forum ).
So, why did I write it? Mostly because I looked at the other tutorials out there and found them really really really bad. The basic "qualification" for writing a tutorial is knowledge of a subject and a willingness to sacrifice your time. Not really all the much more.
The biggest thing though, I vetted my tutorial, this one and all others I've written, and respond to the feedback of others. If you make a mistake, address it. I was really lazy about my const-ness for example. If you don't really understand the topic you are writing about, please just don't do it. We all make mistakes, it's a matter of fixing them, as if you make a mistake in a tutorial, its magnified many times over by the people that read it.
That's the painful part of it. Many people are writing tutorials, or worse, recording screencasts and teaching subjects they REALLY shouldn't be talking about. They perpetrate harmful falsehoods, or worse, teach outright bad information. I have heard this complaint levelled against The New Boston, many many many times, although I've never personally gone through his tutorials.
This ranks up with people making language recommendations in the beginner forums, who have no experience. It's nice that you want to help with your 2cents, but in many cases, you in fact aren't helping. You can't honestly comment on a programming language's merits for example, until you've had years of experience, with i and other languages. Otherwise you are mostly just spreading misinformation and hearsay.
I remember you specifically, on these forums when you just joined, creating a tutorial at the same time you were fumbling through the basics of C++. You took a lot of flak for it here too, and pulled your tutorial down. You've gained a deal of experience since, so I am not making any acquisitions but generally you shouldn't make tutorials before you really understand a concept. Instead perhaps release it as a developer diary, there is a difference.
The final thing to remember, especially if you are going to create tutorials or guides, or whatever... a lot of people on the internet are dicks. Truth told though, they are mostly a minority. When I do tutorials, even if I make a mistake or outright get somethings wrong ( we are all human ), I find the majority of people are incredibly thankful and pleasant over all.
If you are doing a tutorial series, vet it here. Don't post it as a tutorial, post it as a WIP. The community will do a damned good job of letting you know if you are ready or not to be creating tutorials on the subject or not, and if you incorporate the best of the feedback, your tutorial will be all the better for it.
One other thing to keep in mind is, you will also run into situation where people disagree with *HOW* you do something... this is the art side of programming coming to the fore. It is quite possible for both parties ( you and your criticizer ) to be right, or both wrong. So just because someone disagrees with you, it doesn't mean you are wrong.
Finally, if you launch an application in Visual studio with CTRL + F5 ( I believe thats the key combo ), it will automatically prompt for a keypress before closing the console window.