But seriously; I'm not planning to teach my kid to code unless he is really interested in it by himself. I rather have him play outside.
But seriously; I'm not planning to teach my kid to code unless he is really interested in it by himself. I rather have him play outside.
By saying "teach my kids to code", I don't imply "forcing my kids" into it. Just introducing, letting them experience and know it exists, what it's for, how it works.
If I don't expose them to coding, how could I ever know they're interested or not?
A tangent:
The two generations before mine worried too much about letting children "just play". Life was too tough on them when they were kids. And they went to the opposite extreme: made life too soft for me as a kid.
I grew up with a completely wrong vision of life and the world. I entered youth totally unprepared. It's anectodal and I bet there are people who had a too soft childhood with only play and managed it differently, but I'm going to find a better balance for my kids as they grow.
I want to smoothly and gently introduce pieces of adulthood to them, so that when they reach maturity, they're better prepared to be happier, more confident and independent.
> If I don't expose them to coding, how could I ever know they're interested or not?
About this one; programming nowadays is not some obscure niche thing that it's impossible to come by unless introduced by someone else. I started my programming career (being paid to do) when I was a teenager. There was no-one using computers around me let alone knowing what programming is to introduce it to me. I believe nowadays everyone in a somewhat developed or developing country will have the opportunity to choose whether to learn coding or not.
There is no obvious way an avid user of an iPhone or iPad might be exposed to anything resembling programming without seeking it out.
The same is more or less true with desktop os
In the 70s/80s home computers dropped you into a programming environment immediately or a programming-like environment (the shell or command prompt). In the 90s this was less true, but it still wasn't a huge distance from launching to accessing a programming environment (and on Linux and BSDs you still typically started in the shell). In the 00s and 10s, on macOS/Windows/Linux you can still get to a programming environment or shell easily enough (and macOS and Linux generally come with a basic suite of programming tools like compilers and interpreters), but the "distance" for the user has been increasing. If you want even some common tools you have to download them instead of having them immediately available, or in macOS you have to know that there is a terminal which provides better access to the supplied development tools.
Mobile devices have always been behind on this, but they've become an increasingly common first computer for many which skews the relationship that people have with computers away from seeing them as tools to manipulate (via programming and scripts) to appliances. They have more in common with embedded systems like the Tivo or video game consoles than with PCs, providing users with a preset script on how to use them and not the more open-ended model of PCs.
Not debating you but I find it interesting how both your comments _differentiates_ "learn programming" vs "playing with toys".
When I learned coding at age 11, "programming a computer" _was_ "playing with a toy". Programming wasn't an "adult" job that grownups did. Instead, programming was like playing a music instrument or painting art with brushes.
That said, I agree that not all kids exposed to programming will think of it as play.
Just like there's recreational mathematics, a lot of programming can be "recreational", something for play not for "serious" work (even if it happens that the serious bits follow from the play).
edit: just to add, they still do lots of outside stuff, but it's not like before.
Rules and limits are important and I agree the screen offers quicker gratification, so we as parents must set and enforce those rules.
That said, this changes the subject a bit, as we were talking about learning to code.
That's empathically not an instant gratification and we should not equate time spent in front of screen with time spent learning, expanding understanding of logic, cause and effect, structure, etc. And while kids are happy to spend hours gaming, I haven't seen many (in my social circle) that would be happy spending hours debugging some Python, Lua or Sketch code.
Presumably the alternative to teaching them programming, is spending time with them some other way.
Exposure to things is key.
Yeah, we bought him a nintendo whatever-they-were-called when we got home.