Also I will put my whole life to programming! That's what I'm planning to do. Computer is my addiction. Not just games - whole Computer, all processes, etc. But I wanna become a gamedev, because people need games to refresh their soul. It's art, it's refreshing, that feeling of accomplishment, when you start from scratch and build a successful game!

You description of yourself almost matches with mine word for word :D

I began with game developing about the same age as you are now, and my first "utility" of choice was Visual Basic.Net + XNA Framework 2.0. I know, poor choice, but VB was the only language I was confident with.

My first "projects" were nothing better than simple tasks, things that I consider trivial now like shooting ducks flying on screen, moving objects on screen using the keyboard etc. just to learn though process and and logic behind game. On lots of those test projects I lost my interest fairly fast (and since XNA didn't have VB support at that time, I had to c/p code from one tutorial to get the same thing I get by using XNA game creation wizard for C#), never finishing them, but regardless of that I got valuable knowledge that I could use and improve in later projects (one of them is unfinished Breakout).

Few years after my last VB project I switched to C# and continued working with XNA; one of projects of that time was moving a box with orange stick of it around the screen - something that is currently becoming my own clone of Battle City! Mind you, compared to many people here, I'm still very inexperienced in game developing.

So, what did I want to say with all this wall of text (which is something more experienced people are always emphasizing, so I'll end up repeating them):

• Start from the very basics; how to make something appear on screen, how to control object on screen, how to prevent it to go off the screen etc.
• Define small, simple projects you can finish with current skill level while learning something new. There are game order you can follow (like Pong => Snake => Asteroid) but it's better if you do what you want.
• Use tutorials and examples for reference but not as a source. In other words, don't copy-paste existing code but try to reproduce it yourself. You'll understand the logic behind code much better that way.
• Be ambitious, but take one step at a time. With time, you'll be able to make your "dream game" without problems.

Good luck!