I don’t know, I’ve never had any problems with tutorials. Usually I start with the tutorial, then I will apply the knowledge to some real problem that I want to solve, then I’ll look up the tutorial information again to find out why some decisions have been made in that way.
One very important thing is that tutorials can tell you the intentions of those who made the language, library or framework and how it is supposed to be used. This is very helpful if you can see it with real code examples and examples that are tied together to an application that actually works. Because sometimes the documentation only covers some slices of information.
So basically you’re right, after reading a tutorial you won’t know everything about a language and you won’t even know and understand everything that you’ve read with in the tutorial. But to me it’s still worth it...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don’t know, I’ve never had any problems with tutorials. Usually I start with the tutorial, then I will apply the knowledge to some real problem that I want to solve, then I’ll look up the tutorial information again to find out why some decisions have been made in that way.
One very important thing is that tutorials can tell you the intentions of those who made the language, library or framework and how it is supposed to be used. This is very helpful if you can see it with real code examples and examples that are tied together to an application that actually works. Because sometimes the documentation only covers some slices of information.
So basically you’re right, after reading a tutorial you won’t know everything about a language and you won’t even know and understand everything that you’ve read with in the tutorial. But to me it’s still worth it...