If you were wanting to build on this, one of the greatest struggles, particularly with children, is syntax and spelling errors. They very often misspell words like "background" when we're teaching web dev, or forget their brackets and semicolons, so their code doesn't run.
If you were to make something similar but in a language they're already learning, such as Javascript, Java or Python (which, in my opinion, are the most common languages taught to kiddos), that might be useful.
Happy to chat more about this if you're looking for more on this perspective.
I can't make sense out of this; what does it mean, in different words?
I'd suggest changing that to something like "with a special sequence of commands".
While one can refer to computer programs as "code", it doesn't work to refer to them as "a code" -- when people read that they'll think of a short sequence of letters or numbers, and it will be confusing.
It gets complicated when you have to build websites and apps to actually solve some kind of business / consumer need, and I would argue it isn't even the programming aspect that makes it complicated. Rather, it's the fact that the thing you're building is built atop a layer of dependencies that you don't really know anything about, who in turn have their own layer of dependencies. To use these dependencies effectively, you need to know about some of the concepts embodied within them, such as a render lifecycle if we're talking about some kind of frontend js framework, knowledge that isn't precisely "programming knowledge".
And I as I mentioned before, this is why I think I'm not too worried about LLMs getting good at programming.
Actually, teaching tabula rasa students might well be easier than teaching people to un-learn whatever made them successful with their first languages or frameworks. We all have lots to unlearn before we figure out what we should learn.
Solving a problem is a complex process that has a small amount of programming even if it is a programming problem.
Programming is communication with both a computer and a person. Have fun!
Software Engineering = Programming + People + Time
The hard part nowadays is setting up the environment. There's so much meta to a language now its scary.
Then everything is thrown in your face and don't explain the fundamentals.
Imagine a bucket, with blue paint. Lets store this information of paint assigned to a variable of "paint_bucket".
Most guides are: "this is a variable, lets define it as blue".. assuming you know what a variable is. Sure it's not hard to follow and understand but for those like me, I need to know.
Letters make words make sentences make paragraphs make chapters make a book.
https://retractionwatch.com/2014/07/18/the-camel-doesnt-have...
But at first glance, this looks SO similar to Python - just teach them to use some parentheses and colons and you'll be learning programming AND learning a very useful language.
I don't like this. It looks like nothing I've ever seen. It will make transition to real languages difficult.
Once upon a time I think Basic was such used as a decent beginner language to quickly outgrow.
See, for instance, https://www.transum.org/software/Logo/
No thanks.
May you'd prefer a native app that can more easily own your machine?
I realize that's not realistic, but I can still choose to live in my bubble, however unpleasant that may be.