eurg comments on Open Thread, September 15-30, 2012 - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (206)
My 7-year-old son likes computer programming and I suspect has a lot of innate aptitude for it. We have worked out a system that for every X minutes of learning he does with me he gets X minutes of computer gaming time. What kind of learning exercises could help him be a better programmer when he becomes an adult? Should I focus on him doing lots of coding or, for example, would he be better served by learning additional math?
For those of you who are adult computer programmers (and please identify yourself as such in your response) what, if anything, could you have done at a young age that you think would have caused you to now be a better programmer?
I am a software developer, and have glimpsed over many similar questions. To summarize: There are enormous individual differences in how one can become a better programmer, and even more so on the opinions on it. It is not even easy to agree on what basic skills should be there at the "end" (i.e., the beginning, after your first two years real experience), much less on how to get those skills.
That said, most commonplace advice is valid here:
On skill-set:
What should I have done? Training self-discipline would have helped (if something like that is possible). Knowing/Having somebody who is actually significantly better than me, and pushing me, would have helped (fuckarounditis on "learning" is too easy to do).
My Opinion: In professional software development there is very little time to broaden your knowledge -- it goes into obscure platform and domain knowledge quite quickly, and Jobs where you do what is actually interesting are in very short supply. However, exactly this broader knowledge is what can keep you afloat even if you happen to be neurotic, unreliable, slow worker*. So: Let him do what is most interesting, but gently guide him to do it just a bit better, and a little bit more diverse than he would otherwise. About interest: Many people say kids usually like somewhat quick results, and things that crawl. Maybe?
Preparatory learning exercises: Sorry, no opinion and idea here. I always liked to take things apart, and sometimes also to put them together (as in Lego Technik models, or -- almost always unsuccessful -- attempts to construct my own). Actually, I think constructing Lego models (or of course anything that is "more real") is great. But then there is the initial caveat of individual differences.
*: I might exaggerate a bit, but not too much.