[jfries]

Imo, it's a bit unfortunate to drill the curiousity out of kids. I'm very thankful for being allowed to mess around unsupervised on my father's work computer as a 7 y/o. Pressed a lot of stuff I didn't know what it did and learned in the process.

[rimliu]

How does this drive out the curiosity? If anything it encourages it: kid should find out that this button does before pushing it. Though to be fair I did my share of button pushing at 5 years old. It was a typewriter at my mother’s work and I taught her a couple of new tricks after finding out what buttons do. On the other hand I struggle to understand people who refuse to read manuals and then struggle for months or even years with some basic functions of the product, when spending two minutes reading the page four of the manual would have saved lot’s of time and frustration.

[Consultant32452]

This is not realistic for childhood curiosity. A 4 year old is curious about things like what happens when I bang a pot on the ground. It's unreasonable to expect the 4 year old to read a manual to inform them it makes a loud sound, and also unreasonable to expect them to know the difference ahead of time the difference in scale of danger between banging pots and flipping a switch. In fact, for most areas of curiosity no such manual exists. Experimentation is the primary mechanism of learning.

[DanBC]

It even has a name - heuristic play.

Here are early years examples, but it applies to all children.

http://www.kathybrodie.com/articles/heuristic-play-a-simple-...

https://schoolhouse-daycare.co.uk/blog/heuristic-play/

[pixl97]

>kid should find out that this button does before pushing it.

I bet you're the same parent that got an infant a toy covered in giant buttons that light up and make noise. We as a society design button pushing as play.

[tempestn]

When I was seven I got a (used) Commodore 64, and learned a ton experimenting with it. Started me on a path to eventually running a small tech company. So I hear you there. My oldest is 6 now, and I definitely want to get her started on similar things.

I certainly won't be giving her unsupervised access to my work computer though. Instead I'll start her on an old laptop with some flavour of Linux, and no internet connection. I'll also take an LVM image, so she can tinker to her heart's content and we can easily revert if it goes wrong. I expect she'll learn far more than she could using my work machine, where there are all kinds of things that could she'd have to be careful with, and that could cost me hours of work (or even worse, potentially, with email access and such).

Separately I'm also introducing her to minecraft, which is fantastic for exploration. Of course it needs an internet connected computer, but there's more supervision for that one when she's outside of the game.

It's funny, thinking back to getting that Commodore 64, I remember the best piece of tech advice I ever got, again when I was 7-8 or so. My parents' friend, who had previously owned the computer (my parents, like most people in the 80s, didn't have a computer) was teaching me how to use the word processor. He taught me how to create a new document, I think, and I was going over the steps, like "press alt, press f, press n..." And he says, no, no... Don't just memorize the steps—understand what they do, and you won't have to remember them. Then he goes through explaining how alt tells the computer you're going to start a command, f refers to the file menu, which has commands relating to... etc. Stuck with me like nothing else, and that attitude was hugely beneficial in not just computer science, but all aspects of life.

It's a bit tangential to the "don't push buttons" thing, but only somewhat. In both case the point is that you want to not just do things, but think through them and understand them. In my mind, that's a great lesson for kids.