4 ms·
I didn't realize the "Scratch" interface was called "frame based editing" [1]. Interesting. My experience with novice programmers is that they have the most pr
by russellbeattie 5y ago
I didn't realize the "Scratch" interface was called "frame based editing" [1]. Interesting.
My experience with novice programmers is that they have the most problems with code syntax and formatting. The fact that one misplaced comma or semicolon can prevent the whole program from running is incredibly frustrating and for many, is a significant obstacle that prevents further progress. I've seen with my own eyes, 10 year olds break down crying in frustration over a missing semicolon.
But I think it's too early to "standardize" on this particular solution to the problem just yet. I feel we need a few more iterations before it is fully baked.
Millions of people around the world code every day at all levels of ability. When a better development system is devised, it'll just naturally take over and we'll see it everywhere. This isn't it yet.
1. https://en.m.wikipedia.org/wiki/Frame-based_editor https://en.m.wikipedia.org/wiki/Frame-based_editor
- carlosperate 5y agoGenerally Scratch-like languages can be referred to as "visual" programming languages, or "block based" languages. "Frame based editors" would be this new combined approach. https://en.m.wikipedia.org/wiki/Visual_programming_language https://en.m.wikipedia.org/wiki/Visual_programming_language
- russellbeattie 5y agoOh, thanks!! I totally misunderstood that. I'm really wish I could edit my original comment as I really misunderstood what I was looking at originally.
- faizshah 5y agoI started programming around 5th or 6th grade with a language called Kids Programming Language or Phrogram it was sort of like an Actionscript-y language. When I was younger I always found it really frustrating to use Scratch and I think that using that more realistic coding environment helped me build my foundation of skills as I learned the basics of syntax, branching, booleans, loops and debugging. I think syntax errors, reading coding and structuring code are all core skills that a young programmer should learn which I think these visual languages hide. I personally recommend teaching kids with a more realistic but visual language like Processing.js: https://p5js.org/ https://p5js.org/ It allows them to stay motivated by making games or other visual projects but it provides the realistic experience of programming in a more simplified language. There's also some great books and resources to teach out of like https://p5js.org/books/ https://p5js.org/books/ and http://learningprocessing.com/ http://learningprocessing.com/
- russellbeattie 5y agoHeh. My son is now in college so it'll probably be at least a good 10 to 20 years or so before I need to teach programming to a pre-teen again, and by then I truly hope we've worked some more things out.