I've bought a X3 and I loved it (with crosspoint). However, the screen broke after just a week, even if I used the official cover all the time. It's a cute gadget but it's too fragile for the intended use: its strength is the form factor, you want to bring it with yourself to read a page in any mobility setting, but its fragility is a critical issue.
I started programming with Modula-2 and I really believe it was case sensitive. In fact I remember the book I used to learn it (Ogilvie) mentioning the case sensitiveness as a peculiarity of the language: "if case matters in natural languages, why programming languages should ignore it"
Yes, I agree, I feel the term "code" potentially misleading. But even "programming" can look as a triviality when presented in schools with no context and simplistic exercises.
https://dl.acm.org/doi/abs/10.1145/3571785.3574125
Yes, I have similar concerns. These models regurgitate previously seen strings, previous benchmarks included. When you try to evaluate their sheer ability to reason on the text, however, they perform poorly.
(Our experiments with GPT-3 are here: https://doi.org/10.5220/0012007500003470)
This ITiCSE working group tried to clarify why we should be interested in programming (not coding) in education: What We Talk About When We Talk About Programs https://dl.acm.org/doi/10.1145/3571785.3574125 (open access)
The current focus on "coding skills" in schools poses the
risk of giving students an overly simplistic and impoverished idea
of what programming means and involves. Let's try to change it!
The code uses excel files instead of matchboxes... It was in fact an example intended to explore further the use of some libraries for office automation. It also allowed for easy seeing of the weights for different choices, still in a structured way even if outside the program itself.