Kind of like saying that ChatGPT is people adding an AI player to the deterministic program of a chat

Except ChatGPT was written from scratch, so not at all like that

Tic-tac-toe is a classical example problem for neural networks 101, kind of a “hello world”

Doesn't change that that isn't how it was implemented to begin with. In your search results there are even people on Reddit asking how to add an AI player to their existing game. Seems like you gave me search results without even looking at them.

It still is

A deterministic program, yes

Plenty of examples out there

You found plenty of examples of people adding an AI player to the game. The game itself is still a deterministic program.

Wrong maths, you say?

Yes. If I want to know what 1+2 equals, and I throw a dice, there's a chance I will get the correct answer. If I do, that doesn't mean it knows how to do Maths. Also, notice where it said "Here's the calculation", it didn't actually show you the calculation? e.g. long multiplication, or even grouping, or the way the Chinese do it. Even a broken clock is right twice a day. Even if AI manages to randomly get a correct answer here and there, it still doesn't know how to do Maths (which includes not knowing how to count to begin with)

a tic-tac-toe machine was “AI”.

No it wasn't. It was (and is) a deterministic program. AI isn't.

unless indicated otherwise by brackets, which is the correct way to indicate this

No it isn't. The order of operations rules are at least 200 years older than the use of Brackets in Maths. Not sure how you think Maths was done before we started using Brackets.

put brackets around it or bugger off.

Bugger off with your disinformation. There are no Maths textbooks which use Brackets for such a basic expression. Students are expected to know the order of operations rules

The rules for order-of-operations are, so far as I know, arbitrary

No, they're not.

Knowing that you’re supposed to do division first isn’t obvious.

It is if you've been to school or read a Maths textbook

correct, per the standard rules

The only rules

I just replied to someone else with the same question. Less can go wrong (but in either case a non-OOP language, like Pascal, is a much better starting point. You should only ever teach students one concept at a time).

• object-oriented (this is their FIRST proper programming language - they don't even know how to write loops yet and you want us to teach them OOP at the same time?! And as it turns out, I had one student who literally could NOT work out how to use a loop - kept writing 20 variables for 20 iterations. i.e. her variables never varied!)
• variables are weakly-typed (use it for anything, whether it's what you first used it for or not, Python doesn't care)
• indentation has to be exact (i.e. no brackets, just exact indentation). I had one student whose program wasn't working, and it even took ME a while to find what was wrong with it (a missing space).

I think there was more, but that's what I remember off the top of my head. If it was up to me then I would've used Pascal - that's what it's designed for! But at least C# has strongly-typed variables, and doesn't care about your indentation (and unfortunately there was no non-OOP language choice available - I'm not sure how this got in the curriculum when every teacher knows you only teach one concept at a time). As I said, many other teachers felt the same way, but couldn't get it past their school admin's.

I, as a teacher, have had to learn several languages, but that's not the dumb reason bit. The dumb reason bit was WHY I had to teach Python, which once I learnt it (so I cold teach it) I could see right away was NOT a suitable language for teaching to Year 7 (who up to now have only used Scratch). I was teaching the U.K. curriculum, and I found out that teaching C# was also allowed - still not ideal, but better than Python for learners -but pretty much all schools were teaching Python. When I dug into it I found I was far from alone in not wanting to use Python... and I also found out the reason schools were teaching Python. It was because from an ADMINISTRATIVE point of view it was much easier for the schools to have us teaching Python. In other words, the office-workers who didn't have to teach it, only had to admin it, were forcing everyone to teach Python because they wanted the lower overhead that came with installing/maintaining that vs. C#. ARGH! All the teachers who wanted to teach C# were running into exactly the same road-block.

For the people saying Python is beginner friendly, no, it isn't. I had to teach it to high school students (I had no choice in the language). Having to have exact indenting, whilst also not caring at all about how you use your variables, not to mention is OOP, is all a bit much for some students, some of whom don't even fully grasp how to use loops yet. One step at a time.

I actually was a teacher for a while (Computer Science and Maths), and I still do tutoring. When I started working with Xamarin, with no prior .NET/C#/GUI experience (just shell scripts and programs in DOS and Unix), it became clear as day to me that no-one at Microsoft had the slightest idea how to teach things. That hasn't changed even now. The documentation is horrendous - they don't even follow basic grammar rules like spell out an acronym in full the first time, so first time you hit one and you don't know what it is, now the document is useless (because they haven't linked to any assumed background knowledge either - have you tried Googling COM to find out what it is?). When I told someone there (who I won't name) they said "it's near impossible to cater for all levels". No it isn't - you start with the fundamentals (or link to them) and build your way up to the more advanced.

Microsoft documentation...

Here's my blog on writing a MAUI UI in C# which illustrates how to write a document (though I realised later I missed linking a few things and still need to go back and fix those) - Creating MAUI UI's in C#

It's also an issue with their templates - there's no such thing as a "blank" MAUI app. They stuff a bunch of stuff in there which violates "teach one concept at a time". I was so relieved when I found out how to make my own templates! (shell be gone! XAML be gone!)

Here are the basic rules of teaching...

I would add to that (for documentation) always spell out your acronyms in full the first time, link to any assumed knowledge, have step-by-step instructions, and make sure you cover different uses from basic to advanced (and don't damn well use Foo Bar - use a real world example).

This whole thread is about buttons