I glanced over your tutorial and I glanced over the replies. I'm not sure, but I think I have some advice.
Any tutorial has to be able to stand on it's own. That is, not only explaining the steps, but the hows and whys. If you include more info along those lines, then your tutorials will be able to defend themselves without you having to spend extra time later to explain things.
For example, your tutorial has taken a few knocks for taking the long way of doing things. If you had taken the time to explain why you are doing things the long way in the tut, then you shouldn't have to come back later to explain or defend. Something like, "I am doing things the long way. There are quicker ways of doing this, but I enjoy the long way because of the level of control and personal satisfaction. I recommend going the long way, then finding the shortcuts that fit your style."
See what I mean?
Of course, you can't plan for every contingency, but trying to do so will seriously help in the long run.
I remember the comments that I had gotten on my first real tutorial. I was kind of confused and dismayed. But I turned it around and learned how to write much better tutorials. After awhile, I could take the simpliest thing and turn it into several pages of goodness that didn't need defending. My tutorials became more complete beyond the steps needed to accomplish an effect or what have you.
I could write several pages on how to write a better tutorial, but I think I've said enough for now.