Quote:
Originally Posted by cottonvibes
well, i would recommend you be "very descriptive" instead of simple.
i remember when i was a noob a lot of tutorials would tell me what code simply does, but it wouldn't explain descriptively how the code works, and why we were doing it that way.
so, i didn't learn much from those tutorials.
if you don't explain why and how the code works, then you'll only be teaching the people how to copy and paste.
(this is just a general suggestion, i wasn't in your old class so i don't know how you taught the stuff)
|
while i understand your point and i totally agree with that it seems like you havenīt checked my previous lessons because otherwise you wouldnīt have written this... in my lessons i tried to keep things as simple as possible but also explain every single step and not skip them and say(we will explain that later etc.) as many books does. one of the books i used to learn C# was nice but it kept me showing C# stuff and saying "we will explain that later or you will see it later" so i just stay like "WTF???" and was a bit confuse because of that.. of course my C/C++ knowledges helped me to move fast and understand everything very fast because of the similarities of C++ and C# syntax-wise.
__________________
Current development tools:
Visual C++.net, Visual C#.net
Visual VB.net, Visual Webdeveloper.net
Bloodshed Dev C++, Borland C++
Visual Basic 6