There is a saying that the only way to learn is from mistakes. Only geniuses learn from others.
I think this applies in a high degree to programming. That is why it is difficult to read good books that show how it should be done. You have to do the mistakes yourself. And so I agree with what many state above, start writing code immediately. When it doesn't work, or you have problem to find out how to design it, then you go looking for answers in books and Internet.
There is a reason why I didn't recommend a specific language. It doesn't matter. Learn Prolog as your first language. Learn Fortran. Heck, learn Malebolge. Doesn't matter.
What does matter is your incessant worrying about the "right" and "proper" and "correct" way to do things, which is going to do nothing but hurt you in the long run.
Don't forget: tutorials are there to show you _how_. You would need to read a book on the language, and spend a while getting your hands dirty to learn _why_. A common misconception is found among people that flock to tutorials; most people wind up just copying and pasting the code, then looking for a tutorial for the next thing. Tutorials work best when you already understand why it works. It's like reading a book on poetry to learn the English language.
Just adding another reason to not start with tutorials that aren't part of documentation teaching a language from start to finish.
