ey codemasters q3w
Re: ey codemasters q3w
Also some knowledge about how a computer works on a low level is helpful. It's harder to really understand programming when you don't understand how memory works or what a clock cycle is, etc.
Re: ey codemasters q3w
C# is awesome. I program it daily and find it the best mix for speed and readability. A few months back I wrote an Android app (Java) for my company; I hadn't touched Java since Uni but it's scary how close the two languages are
.
Python seems to be the current big thing though, it's relatively easy to learn and can do pretty much anything.
What about something hardware based like an Arduino or RaspberryPI? Learning with something physical might be a better way of learning how programming works as you actually see a result.

Python seems to be the current big thing though, it's relatively easy to learn and can do pretty much anything.
What about something hardware based like an Arduino or RaspberryPI? Learning with something physical might be a better way of learning how programming works as you actually see a result.
Re: ey codemasters q3w
I don't agree. For basic, starter level programming it's really not required to know how a CPU works or what different types of memory there are, mostly because you won't run into any limits imposed by these factors. Don't get me wrong, eventually when you work on really complex systems you need to know more of this stuff, but with your first Hello World program, hardly.mrd wrote:Also some knowledge about how a computer works on a low level is helpful. It's harder to really understand programming when you don't understand how memory works or what a clock cycle is, etc.
Re: ey codemasters q3w
How about trying Unity? You can either use C# or Javascript, it's got a very nice IDE and all the tooling you'll need. And it's free.
Re: ey codemasters q3w
Aren't there currently better ways of learning programming than simply starting with "hello world"? I understand that basic foundations are important, but it's also really dry and makes one lose interest rather quickly. Perhaps r3t has the right idea by suggesting that one should start with a pre-existing set of tools and start with small modifications to them. It's much more satisfying seeing some small physical change rather than seeing your string being printed to a CLI window.
I'm not a programmer but would like to learn, and I've found that my main stumbling block was getting bored with writing shitty exercise problems that weren't any fun or satisfying to work with. So I tend to gravitate to other things like web and video game development, where I can F5 or compile and see significant changes immediately.
I'm not a programmer but would like to learn, and I've found that my main stumbling block was getting bored with writing shitty exercise problems that weren't any fun or satisfying to work with. So I tend to gravitate to other things like web and video game development, where I can F5 or compile and see significant changes immediately.
[size=85][url=http://gtkradiant.com]GtkRadiant[/url] | [url=http://q3map2.robotrenegade.com]Q3Map2[/url] | [url=http://q3map2.robotrenegade.com/docs/shader_manual/]Shader Manual[/url][/size]
Re: ey codemasters q3w
If your son wants to make games, find a game he likes and plays a lot on the PC, and get him started down the road of modding it.
I don't feel the goal is to teach him a particular language, but to spark the interest in the right context such that all the frustrations of learning programming as a kid on your own seems worthwhile and keeps him motivated.
I don't feel the goal is to teach him a particular language, but to spark the interest in the right context such that all the frustrations of learning programming as a kid on your own seems worthwhile and keeps him motivated.
Re: ey codemasters q3w
inolen's idea is good... after all, interest in video games is a bit too open ended. does he want to code, design, model, direct? do you know?
moding somethign that is already there will wet his appetite of actually creating something and having relatively instant gratification from the work he puts in it. starting him from the nuances of what variable type you should use ( float, int, double..), and code syntax/semantics just to print out "hello world" doesn't sound like the most kid friendly way to go about it. He will naturally gravitate to that lower level shit by himself once he starts to master the limited possibilities of simply moding existing games and seeks out bigger challenges/possibilities.
Starting at those lower levels might actually scare him off , by thinking that he was not cut out for shit like that in the first place.. which could not necessarily be the case.
moding somethign that is already there will wet his appetite of actually creating something and having relatively instant gratification from the work he puts in it. starting him from the nuances of what variable type you should use ( float, int, double..), and code syntax/semantics just to print out "hello world" doesn't sound like the most kid friendly way to go about it. He will naturally gravitate to that lower level shit by himself once he starts to master the limited possibilities of simply moding existing games and seeks out bigger challenges/possibilities.
Starting at those lower levels might actually scare him off , by thinking that he was not cut out for shit like that in the first place.. which could not necessarily be the case.
Re: ey codemasters q3w
True speak, 'spose I'm thinking further down the line.Eraser wrote:I don't agree. For basic, starter level programming it's really not required to know how a CPU works or what different types of memory there are, mostly because you won't run into any limits imposed by these factors. Don't get me wrong, eventually when you work on really complex systems you need to know more of this stuff, but with your first Hello World program, hardly.mrd wrote:Also some knowledge about how a computer works on a low level is helpful. It's harder to really understand programming when you don't understand how memory works or what a clock cycle is, etc.
Re: ey codemasters q3w
[color=red] . : [/color][size=85] You knows you knows [/size]
Re: ey codemasters q3w
lots of good advice here for sure
i think the c and all that is good especially with all the ms tutorial tools and all that.
inolen thx for your insight because it really kinda hits on the core of what its about, getting the "fever" and using trial and error and cause and effect.
my son is 8 and he doesnt do alot of pc games but some for example the armourgames type online games . so maybe there is an "in" using something like crush the castle code?
his main like is mario , all mario , so i guess some n64 rom editing tools maybe?
again thx guys cuz i am cluless at this stuff.
i think the c and all that is good especially with all the ms tutorial tools and all that.
inolen thx for your insight because it really kinda hits on the core of what its about, getting the "fever" and using trial and error and cause and effect.
my son is 8 and he doesnt do alot of pc games but some for example the armourgames type online games . so maybe there is an "in" using something like crush the castle code?
his main like is mario , all mario , so i guess some n64 rom editing tools maybe?
again thx guys cuz i am cluless at this stuff.
it is about time!
Re: ey codemasters q3w
Oh hey, if you've got an xbox 360 your son might like a game called Kodu. It's basically a graphical coding tool that teaches the basics of coding in very easy to use graphics instead of words. You should check it out, I've had fun playing with it and you can make a fair number of different types of games with it. Well worth it and an easy way to learn how programming works on a very superficial level.
Re: ey codemasters q3w
Example of what it looks like. Would be great little game for a would be 8 year old coder.

