Teaching My Daughter To Code
blogs.kent.ac.uk
Teaching My Daughter To Code
1–10 of 19 posts
Re: Teaching My Daughter To Code
#2Reminds me of Turtle Graphics from Logo ( http://el.media.mit.edu/logo-foundation/logo/turtle.html ). Interesting that programming at this basic level has been unchanged for so long...I guess that means we got it right at the beginning!
Re: Teaching My Daughter To Code
#3A long time ago, I also made these kinds of programs. That was on a PET 2001, and I didn't have the luxury of bitmaps back then. I would use the PET's graphic characters as 'actors', and POKE them to the video memory. It started with simple balls, but soon my 'actors' grew into sprites made up from multiple characters (with a square, a few line graphics and a ball you could make a little fellow). POKEing all these characters from BASIC became a bit slow, and that was the moment I started learning machine language (necessity is the mother of invention), and from then on I wrote my PET games in 6502 assembly. That made them blindingly fast! (And very prone to crashing, too ;-)
Re: Teaching My Daughter To Code
#4My first (real) programming experience was with PHP when I was 14. Before that, I fiddled around with a bit of flash and ActionScript. I found it so much easier to learn by actually having a project and working out how to make it a reality as opposed to just reading about it in a book.
Re: Teaching My Daughter To Code
#5Brad Fitzpatrick says in "Coders at Work" that his father taught him to program when he was 5 years old.
Re: Teaching My Daughter To Code
#6I was learning C when I was six years old. Definitely helped that my older brother (then 11) was the one teaching me— I wonder if having young children learn from older children might be good advice in general?
Re: Teaching My Daughter To Code
#7This reminds me the story that my deceased father told me. Once upon a time when the c64's reigned in Turkey, He asks me to write down some of the programs distributed with Commodore magazines. Yes, these magazines consisting of 5-6 pages full of GW-Basic code and which are mostly incorrect or incomplete :) And he adds, "Than you who never stands up from the desk did not touched the computer at least a month" :)
Re: Teaching My Daughter To Code
#8I was learning C when I was six years old. Definitely helped that my older brother (then 11) was the one teaching me— I wonder if having young children learn from older children might be good advice in general?
It's possible great advice. See these two TED Talks by Sugata Mitra for evidence:
Re: Teaching My Daughter To Code
#9Reminds me of Turtle Graphics from Logo ( http://el.media.mit.edu/logo-foundation/logo/turtle.html ). Interesting that programming at this basic level has been unchanged for so long...I guess that means we got it right at the beginning!
I have fond memories of using Turtle in primary school. It had much more of a positive impact on me than re-typing code from a book into my Amstrad CPC-6128!
Re: Teaching My Daughter To Code
#10I was learning C when I was six years old. Definitely helped that my older brother (then 11) was the one teaching me— I wonder if having young children learn from older children might be good advice in general?
I first coded when I was about the same age, but at that point it was mostly type out programs from magazines and making minor tweaks (this was in Atari Basic). When I was 9-10 I was writing my own simple games in Amiga Basic and later CanDo. When I was 13 I started learning K&R C and then later Quest-C (A VB like tool for C).
I remember there was one other kid in my year at school who was better at C than me at the time, so I don't think I was that unusual.
I think it easy to underestimate what kids are capable of.