Thanks. It's a very 21st Century phenomenon that I've unfortunately run into many times

that’s not a problem unique to python

No, but it's a bigger problem for C# than is is for Python (though this is changing now), so all the U.K.-based schools were teaching Python, rather than the more-appropriate C#. That was my original point - that's the dumb reason I had to learn Python, school admin's wanted the lower overhead of the worse language.

Oh! I just remembered this video. If you wanna know how students can struggle with pseudo code, watch the video. I use this video when I teach algorithms (students are even worse at that than pseudo code).

Pascal was the first real language I learned (after basic)

Same. Taught myself some Basic in high school (first on a school computer, then we got a computer at home), learnt Pascal in 1st year Uni (programming basics - wrote a bunch of stuff for myself in Pascal for my computer) then C in 2nd year (OOP), and then Assembler in 3rd year. Later I taught myself (with the help of some books and courses.... and intellisense! 😂) C#.

YIj54yALOJxEsY20eU has compromised on their privacy values by not including a special character in their username.

They're just trying to convey they're not THAT strong. 😂

don’t have to learn about indenting until you cover flow control

Which is one of the very first things they're taught - "hello world", variables ("Enter your name", "hello {name}"), branches, and loops, in that order.

I’m not sure I can think of a language that would be better suited to learning

Pascal - it's what it was designed for. Variables, branches, and loops, with strong types and optional indenting. Once people have a handle on that, THEN move onto OOP.

Yep, I've been actively promoting programming.dev any time the topic of StackOveflow has come up.

Some of my intended audience don't know about Lemmy yet... hence the talk. :-)

explaining others also helps me understand it better.

There's a saying - if you want to learn something then teach it (even to a rubber duck ;-) ).

That's ok. Thanks for being big enough to admit you were wrong - these days a lot of people aren't!

That's ok - a lot of people weren't.

This would be correct if the post was about switches (which TBF many people made that mistake, including me initially), but it's about buttons - buttons should show what action will result from clicking on them. e.g. "Cancel" on a button which is going to cancel your process. For a play/pause button it should show play if you're paused (if I click on this it will start playing) and pause if you're playing (if I click on this it will pause).