I've generally found that when I'm faced with some task that I don't know how to begin to approach I am more likely to be distracted by things.

The best suggestion I have is to try to think small for awhile. Don't even think about making a game. Don't think of releasing anything to the public. Instead maybe think about making a number of projects (I call them labs) to implement various elements of a game. Stuff like trying to get a small 2D image on the screen. Then make it move with the keyboard. Animate it. Create multiple instances of that image (as many as you can).

If doing stuff like this is too difficult to wrap your head around at the moment then there's some fundamentals you need to work on first. If you don't know what those fundamentals are then you should ask someone here what sort of prerequisites you should be looking at. If that still ends up being too much, find out what the prerequisites for that might be and so on.

Think of it all as building on a plan to achieve your goal. Let the plan change if it has to. If you feel like taking a bold leap towards something that's a little ahead of you, by all means go for it. But don't beat yourself up if it doesn't turn out. But instead, if you can, try to make sure that everything that you do builds onto whatever you might be looking at in the future. In time you will be able to see how these various things piece together to make a game.

To learn game development you have to do this:

1) pick a language and learn it

2) pick a library or toolkit and learn it

3) Got to a game dev site and ask tons of questions

It is a long, slow process, but that is about as simple as you can make the process, assuming you are going to go to others for art, sound, etc. Otherwise you will have to tweak it and add in any discipline you plan on using; like learning Gimp and pixel art or blender and modeling or learn LMMS or other sound program and create music for the game, etc.

I won't get into my story, but I've been programming for twenty years (started with BASIC when I was 13) and made only two games in that time (pong and vertical shooter). I have battled depression because, thanks to family, doubt myself and abilities to program so I don't join teams or show code much. Don't fall into my loop.

Wow I appreciate all the responses. The book that Saint Retro mentioned seems interesting, I might try it out(The Chimp Paradox). And yeah I just need to sit down and decide if if this is really what I want. If it is, I just gotta stick to one language and figure it out.

I guess I'm just very impatient and I know that I need to learn basics, but I'm still trying to rush myself into the game development even though I shouldn't be.

Linear Algebra it's essential for any type of game you want to make. Find a book and do not read everything until you've have a solid knowledge that you need.

After that you can try to develop some basic games like Tetris, etc. using your math knowledge; if you find that you can't make any progress, read that book again, and try again—that applies to any other type of field.

For more you can think that doing basic games are fun, doing a complex game it's not fun; it requires time, and that it's something that gets more difficult to have as you get old.

While learning programming, try to develop your small games in a organized way; try to use the divide and conquest method to get your precise results, and you probably won't get a headache through that.

Also, C++ it's a industry standard for making complex and basic games. It gives you a low-level approach of how things works, and that approach it's applicable for every other type of programming language. So, between the languages you said, I'd recommend with C++ because most of the materials available online uses that as the implementation (practical application) of a certain subject.

Here, you can find specific solutions for a specific problems; most of the problems that are unsolvable here are those that ask for a general solution instead a specific one, and even this way you can find a good solution. If you ask someone to give you a game, that person won't give how to do a game, instead he/she will ask you what it's the specific problem and try to answer that.

"Learn by doing" it's a good phrase, but not be confused with "learn by doing without knowing nothing".

To learn game development you have to do this:

1) pick a language and learn it

2) pick a library or toolkit and learn it

3) Got to a game dev site and ask tons of questions

4:Eventually join a team, having teachers or teammates is so beneficial! having somebody to work with.

I'm extremely hesitant to agree with that. I have severe confidence issues because the teachers, teammates, and other programmers I worked with treated me like my knowledge and mental capacity was one step above that of a rock. I would stress extreme caution when seeking to join them.