Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualDareDeveloper

Posted 05 July 2013 - 02:24 PM

I kinda know what you are asking for.

I think your assessment that your know a lot about programming is not quite right, though. You probably have a solid idea of the basics, which certainly is not nothing, but there is still a lot of big picture knowledge you need to learn.

Usually I would agree that learning to program / thinking like a programmer in general is more important than examples of how something is done.

 

But I didn't make any progress until I found a follow-along-tutorial that happened to explain the thoughts / reasoning behind the taken steps.

So I actually like your take on learning. I read "The First 20 Hours" (first20hours.com/‎) and love the message:

You should only learn enough theory that you can start doing something right away (and before that you should know your goals ... more detailed than you have outlined them).

You need to break your goals down into chunks, as many others here have said here. Making smaller games will help you get that big picture knowledge.

 

Unfortunately I don't know of any tutorials that teach the reasoning ... and I don't know of any source code on Github that you could analyze.

Maybe somebody can point something out.

Maybe you can also prove that you have the big picture knowledge that we think you lack.

 

I think Nehe might still be a place with some info on 3D Graphics programming (http://nehe.gamedev.net/). The codebase was improved ... not sure if all links point to that codebase. Maybe somebody here has an opinion on the state of those resources?


#2DareDeveloper

Posted 05 July 2013 - 12:09 PM

I kinda know what you are asking for.

I think your assessment that your know a lot about programming is not quite right, though. You probably have a solid idea of the basics, which certainly is not nothing, but there is still a lot of big picture knowledge you need to learn.

Usually I would agree that learning to program / thinking like a programmer in general is more important than examples of how something is done.

 

But I didn't make any progress until I found a follow-along-tutorial that happened to explain the thoughts / reasoning behind the taken steps.

So I actually like your take on learning. I read "The First 20 Hours" (first20hours.com/‎) and love the message:

You should only learn enough theory that you can start doing something right away (and before that you should know your goals ... more detailed that you have outlined them).

You need to break your goals down into chunks, as many others here have said here. Making smaller games will help you get that big picture knowledge.

 

Unfortunately I don't know of any tutorials that teach the reasoning ... and I don't know of any source code on Github that you could analyze.

Maybe somebody can point something out.

Maybe you can also prove that you have the big picture knowledge that we think you lack.

 

I think Nehe might still be a place with some info on 3D Graphics programming (http://nehe.gamedev.net/). The codebase was improved ... not sure if all links point to that codebase. Maybe somebody here has an opinion on the state of those resources?


#1DareDeveloper

Posted 05 July 2013 - 12:08 PM

I kinda know what you are asking for.

I think your assesment that your know a lot about programming is not quite right. You probably have a solid idea of the basics, which certainly is not nothing, but there is still a lot of big picture knowledge you need to learn.

Usually I would agree that learning to program / thinking like a programmer in general is more important than examples of how something is done.

 

But I didn't make any progress until I found a follow-along-tutorial that happened to explain the thoughts / reasoning behind the taken steps.

So I actually like your take on learning. I read "The First 20 Hours" (first20hours.com/‎) and love the message:

You should only learn enough theory that you can start doing something right away (and before that you should know your goals ... more detailed that you have outlined them).

You need to break your goals down into chunks, as many others here have said here. Making smaller games will help you get that big picture knowledge.

 

Unfortunately I don't know of any tutorials that teach the reasoning ... and I don't know of any source code on Github that you could analyze.

Maybe somebody can point something out.

Maybe you can also prove that you have the big picture knowledge that we think you lack.

 

I think Nehe might still be a place with some info on 3D Graphics programming (http://nehe.gamedev.net/). The codebase was improved ... not sure if all links point to that codebase. Maybe somebody here has an opinion on the state of those resources?


PARTNERS