Can kids under 10 be possibly taught coding, without even mentioning the word syntax to them ??🤔🤔🤔
Can kids under 10 be possibly taught coding, without even mentioning the word syntax to them ??🤔🤔🤔
Weird question. Can a child under 10 be taught coding? Yes, I started learning under 10. Was the word syntax used? Fuck if I can remember. I don’t think it would have mattered. Why do you think it matters?
Yeah, kids are really smart.
Yes. In school we had a course where you programmed a virtual robot navigating through a maze.
The commands were simply "go forward", "turn left", etc.
Then they introduced basic programming principles one by one.
Simple loops, conditions, outputting messages, etc.
The following year, they switched us to programming in Pascal and it was basically the same thing, only now we had to learn some simple syntax.
Yes, when I was a kid in school in the 90s we learned logo and qbasic.
http://www.petesqbsite.com/sections/tutorials/tuts/felix_qb_for_kids.htm
Logo uses a little turtle to draw, it was a blast!
Check out scratch (or even scratch junior).
If they like robots, go for a micro:bit or a similar kit. The ide is from Microsoft, but microblocks.fun is a good alternative
Just call it something else 🤷
We were taught basic programming when we were 6. It was Kyiv, 1992.
I started learning when I was ten, so I’d say yes. That was almost thirty years ago when learning to code was less accessible, so having more resources should make it even easier.
I was learning BASIC on a VIC-20 around that age.
I've never used it, but people I work with teach Scratch to in their spare time. I quick search suggests it is years 8+. I guess it's more programming than coding, but could be a starting point and lead into coding under 10?
I got my kids started on Scratch - I recommend it! Syntax is communicated with puzzle block shapes. Statements have a tab on the bottom, and a matching slot on top; number and string values are pill-shaped; boolean expressions are diamond-shaped. If the pieces fit together, it's a valid program.
more programming than coding
What's the distinction?
Good question!
"Programming and coding are closely related but not the same. Programming is the process that covers problem-solving, designing, building, and maintaining software, while coding is the step of writing the actual instructions in a programming language. Both are important and work together to create complete software solutions." - Geeksforgeeks
When I was a kid, we had a class on Logo in, I think, 4th grade? (It was either that or 5th grade.) It wasn't particularly hard to make various geometric drawings with it, but it also wasn't clear how to use it to do anything beyond that.
I used to tinker with Visual Basic on the school's computer lab at recess sometimes around then. One of the people who ran the lab showed me just enough to try to make a calculator UI (e.g. push number buttons and have it add numbers to the display) but didn't really explain the principles enough for me to get further than that. (I think he loaned me a book on BASIC that I tried to read on the school bus, but I couldn't get very far with it at that age.) I ran into a macro virus back then as well, and I was able to understand the logic for erasing files on a particular date when it was pointed out, but I wasn't able to make something like that or analyze it myself at that age.
I also tinkered with HyperCard and some other creative software at home at around that age. I did not understand HyperTalk but could do a few simple things. I also stumbled into AppleScript but didn't understand it. I think I recorded macros with it, and tried to modify what it spat out without much success. I remember running into something about timezone conversion that was really cryptic to me as a kid -- that might have been the first time I encountered the term "GMT"? There's a lot of little things like that which will trip up a young beginner...
I think I also checked out a book on Java from the library that had a CD-ROM with the compiler on it somewhere in that 4th~6th grade age range (don't remember more specifically when) -- I was definitely too young to for that. I was able to install the software, type in a program from the book, and make it run but I wasn't able to do anything beyond that with it and it was too tedious for me to persevere through the cryptic parts when I was that young.
Somewhere around 5th ~ 6th grade I found Game Maker and taught myself that by tinkering with the sample games. For example, by making alternative level layouts for the Pac-Man clone and adding in some simple things like one-way teleporters. I used the drag and drop interface at that age with one of the really early versions before the 4.0 UI re-design -- it was a lot more approachable as a beginner, IMO, before that redesign. (With the changes it was better for me as a hobbyist as I got older though.) I eventually taught myself how to use its scripting language through a mixture of reading the manual and trial-and-error. The manual didn't explain the basics of programming very well, but the reference documentation for it was easy enough to understand that once I got a handle on the basics I could do a lot with it. I'm not sure how old I was when I got a good handle on it. Maybe 7th or 8th grade? I was able to make some fairly complex things from scratch by 9th grade and taught myself C++ in high school.
I definitely could've learned a lot more conceptually earlier if I'd had more direct mentoring from someone who could code; I had to figure out a lot by trial and error. My knowledge of math, reading ability, etc. limited my ability to self-teach from books. People around me were also rarely able to answer questions when I hit something above my expected grade level (e.g. I remember asking what "sigma" meant to a math teacher in 7th grade after encountering it in a book and she didn't really understand my question and told me it was another variable like x instead of recognizing that I was asking about summations but didn't know that word yet... I eventually made the connection between it and for loops but I could've understood it then if I'd had the vocabulary to ask the right questions or had the sample text handy when I asked...) In retrospect, I'm surprised at how bad my teachers in high school were when I tried to get help with figuring out how to move things in circles in a game I was writing -- that was all just basic trig.
I guess to summarize: if they're motivated, yeah, you can get a surprisingly long way very young.
When I was a kid, we had a class on Logo in, I think, 4th grade? (It was either that or 5th grade.) It wasn’t particularly hard to make various geometric drawings with it, but it also wasn’t clear how to use it to do anything beyond that.
This sums up my early experiences with programming. It felt like either pointless flashing lights or building the universe from scratch. These days I have lots of tasks that programming is useful for but for the longest time no sources I encountered ever seemed to talk about what practical use I could put the concepts to.
Telling me about for and while loops and various other things felt like learning by rote and I never got very far. It wasn't until my late 20s when I had a load of tedious administrative tasks to do that I was able to get my teeth into programming.
@e0qdk@reddthat.com 😱😱 communicating with you would help me a lot in my path of mentoring children in transforming themselves into players with bugs and creators of crashes 😆 😆 😆 😆 😆
I started learning BASIC when I was 8. But I'm pretty sure I learned about syntax, too.
What aspects of coding?
Turing Tumble is a marble run puzzle game that's Turing complete, i.e. in the abstract sense, it can compute anything a computer could. It implements bit flippers, logic gates, and memory using falling marbles and levers. Completely mechanical and very tactile.
For textual programming, check out Hedy, a language designed for the classroom. It stands out vs others like Scratch or Snap because Hedy is gradual. A presentation by its creator
I started learning when I was 9. I think to some extent it was easier back then in the 80ies because computers were relatively simple machines. On the other hand I also had to learn English at the same time to be able to read manuals and programming books etc. So I think it must be possible because even if I saw the word “syntax” I doubt I had a full grasp of what it means.
Isn’t that the point of languages like Snap?
The first place to start learning coding is with logic games. Pipe Dream was the OG of this type of game but there are plenty of clones on every platform. It introduces concepts like order of operation and problem solving. And there's plenty of variations besides pipes there's also rivers and streams, electricity and circuits, magic circuits, ect.
The next step would be logic gate type games that teach OR, AND, XOR, ect.
Yes but none of them will be able to say Coq without giggling
Coding is a bit like puzzles. Sometimes the pieces must go together in the right way. But the great thing is, we are cutting some of the pieces so we can change some things, but not all.
Python? Yes
In the 80s I learned logo. I was so young that "repeat" was the longest word I knew how to spell.
Is “syntax” a bad word now? Don’t dumb things down for students, elevate the students!