So, I am trying to organize the information I have gathered on computer programming. I have just been winging it to get things done, but now I want to organize and simplify my understanding and practice of computer programming.

But really, I don't know what I know. I mean, I might think I understand something, but I have no basis to compare my understanding against. I can get stuff to work by some sort of basic hackery, but I don't think I can apply my understanding on more complex things. Programming is so various.

Here, for example, you have so many various questions about computer programming, from so many various backgrounds, on so many various topics, dealing with so many various APIs and tools, using many various programming languages.

It gets to the point that I don't really know anymore what I understand, or what I should understand.

So, I have started to try out making tutorials for my own understanding, and refining them to make them as simple as possible, but the subject of computer programming is so vast and various, I get overwhelmed.

This is the usual case when I am diving head first into something new, but eventually I come out with a solid understanding.

Right now I am bouncing back and forth between two languages and about 3 different APIs. I am learning the programming languages as I go, and modifying my understanding of them as I go (this is not the normal way I do it, but this is the faster way of doing it, which is what I am aiming for because I tend to over-plan.)

Even when you get the programming part down, you still have to wonder about what platforms and stuff you want to run it on, and what hardware will be able to run it. If you are trying to make an app for android, well, you know what that means....

So, I need some help. I am simple minded, and I figure I don't understand anything well enough if I can't teach it to a little child. So I need some direction on how to organize the topic of computer programming. I am actually trying to create a program that teaches programming, which can be applied to various languages. Things like how to create variables and functions and classes. How to do loops. How to manipulate tables/list/arrays etc. How to use APIs etc. I want to use this program as a base which can be adapted for various languages.

I mean, it could even be a game that teaches game programming workflow. And I want to keep it basic and simple, yet useful.

Any tips?

Edit: I just realized that the best way to start is to teach it using pseudocode, and then looking at syntax. Still need more tips though.

To me it seems as if you do not over-plan ... I guess you just have a hard time coming up with a structure in the planning phase and justify jumping into application of something you read by calling the problem over-planning.

I know a few people who are really good at researching efficiently, but it is a skill that needs to be learned and honed.

I think "The First 20 Hours" (by Josh Kaufman) kinda helps ... he outlines how much he researches before he figures out how to build a skill. And he defines a target performance level ... good stuff IMO.

Writing papers ... kinda like scientific papers can help too. You have to describe what your goals are, come up with a structure, write down what the result of your research is and you have to be able to explain it and read about its context.

There is a Programming Paradigms box in some Wikipedia articles. I like it as a big picture overview over programming:

http://en.wikipedia.org/wiki/Object-oriented_programming

Other topics have pretty good entrance articles as well ...

the http://en.wikipedia.org/wiki/OSI_model OSI model if you want to get into networking etc. ... you need to dig up those resources for areas that you want to tackle.

Stealing from what universities teach is not a bad idea either ... you can still cherry-pick instead of learning everything they would throw at you.

While it can be fragmented a lot of the concepts behind it are the same no matter what language,API or tools you use. You may type different things or call different functions but they can be semantically the same. So one thing Id advise (although you may not want to do it) is stick to one language and get a decent understanding of it. Jumping between languages might make things more difficult. But I found once I understood the concepts in one language I was able to learn another much faster as I was mostly just learning the syntax.

Also dont forget, you never stop learning!!

Hi,

As I suggest to many beginner level and intermediate people here, you need to settle on one comprehensive workflow pipeline of applications and software to complete projects. It is very much a grueling step by step cycle of coding, testing, and debugging. Many are tackling advanced coding challenges without even realizing it. Coding courses and tutorials are critically important to complete.

Common strategic mistakes by beginners, for example, is that that are reaching too low in coding to get a grasp of the big picture - sort of like digging too deep with not enough skill and equipment. Remember the old cliché, "They can't see the forest for the trees!" ? Another common strategic error is to not constantly keep in mind modular coding. The programmer should be able, if done right, to turn ON or OFF sections of coding by using permanent or temporary interfaces between source code and the particular module of coding. Modular coding also allows the developer to swap sections of coding to test for performance or bugs, which is common with class files, jar files, and dlls. A good game engine comes with some of the tools to allow this and also connect with IDE or SDK to open relevant libraries and exploit them. Nice, thick, recently published book in the language of choice would be a great help to you to finish, maybe even a couple times. Choose one that has work assignments in an IDE and/or game engine. There are hundreds of such books published in the last two years covering all kinds of programming subjects.