Chris BONDE wrote:
I am not sure if I explained my thoughts well enough when I said in a
previous response
snip
A To do would be similar to a basic recipe on How to make a chocolate
cake with black cherries. Ingredients, mixing, baking and serving.
Nothing on how to change, improve, learn about cake baking. Just how
to bake a black cherry chocolate cake.
A Tutorial would be similar to explaining all about cake making,
chocolate requires coco, white requires vanalia etc. The presentation
would include whether the icing, frosting or not would be maple or
marzipan.
Your analogy to a recipe for a How To is smilar to my opinon. Not sure I
agree with you on the Turorial however. From your description it is
closer to what I would see as a academic text. What I mean by this is a
seperation between generalized theory and theory applied in a specific
context. This is where cooking may break down as a vheicle for
explaining the differences.
Turning to the subject of software instead, I would put it this way. If
one writes an article regarding the Relational Data Model, what is a
tuple and a constraint for example, without regard to a particular
vendor's implementation then this would not IMO be a turorial. It is an
academic text. However, if one writes an article that covers how to
implement these concepts in a particular package, that is what I
consider a tutorial.
From these definitions then indeed my first article is much more of a
"How To", not a Tutorial.
So given this, only one question remains. After I get done, hoepfully
this weekend, incorporating the changes made by the reviewer and some
suggestions offered by a few others at the Forum - and after changing
the title from Tutorial to How to - jsut where should I upload it to? :-D
Drew
