> No. Those should be done by hand, so kids can develop an intuition for it. The same way we don't allow kids learning multiplication and division to use calculators.

I would think that it would make sense to introduce Python in the same way that calculators, and later graphing calculators are introduced, and I believe (just based on hearing random anecdotes) that this is already the case in many places.

I'm a big proponent of the gradual introduction of abstraction, which my early education failed at, and something Factorio and some later schooling did get right, although the intent was rarely communicated effectively.

First, learn what and why a thing exists at a sufficiently primitive level of interaction, then once students have it locked in, introduce a new layer of complexity by making the former primitive steps faster and easier to work with, using tools. It's important that each step serves a useful purpose though. For example, I don't think there's much of a case for writing actual code by hand and grading students on missing a semicolon, but there's probably a case for working out logic and pseudocode by hand.

I don't think there's a case for hand-drawing intricate diagrams and graphs, because it builds a skill and level of intimacy with the drawing aspect that's just silly, and tests someone's drawing capability rather than their understanding of the subject, but I suppose everyone has they're own opinion on that.

That last one kind of crippled me in various classes. I already new better tools and methods existed for doing weather pattern diagrams or topographical maps, but it was so immensely tedious and time-consuming that it totally derailed me to the point where I'd fail Uni labs despite it not being very difficult content, only because the prof wanted to teach it like the 50s.