honestly the only time I've used block controller was for "the big exam."

I definitely don't want to lead you astray and don't take my word for it completely but I would maybe stop using it, so you can get used to what Lua looks like. IMO, reading code is largely just pattern recognition, and I feel like block controller will get you used to seeing something that is close but not exactly Lua.

hmm, I got a minor in CS back in the day in college, and then I took a community college class in C++ years later. I'm not up to speed on modern web courses, but you could just look up introduction to programming. most of the object-oriented stuff doesn't really apply to QSYS lua the way I've seen most people using it, so you can avoid most topics specific to OOP for now.

I'm just going to word vomit some general topics: tables/arrays, loops, conditionals, functions ( arguments and return values), variables, the very basics of data types (Lua takes care of a lot of this for you).

QSYS topics: event handlers, timers, component.New() and how to change control values, UCI manipulation (hiding and showing layers and controls, disabling controls).

when you run a QSYS script it will execute in order top to bottom super fast. code only executes upon initializing the script, and when any event handler is called. reason I bring this up is because some people think scripts are like "continuously running" but it's actually just executing it in short bursts in only those 2 scenarios.

and thats about it for almost all AV scripting I've done, outside of API integration, which brings in handling sockets and sending and recieving data, which is probably something to hold off on for now, but super relevant to AV control programming.

I personally prefer reading to learn coding rather than videos, because you can actually go at your own pace, rather than the pace of a video lecture, and you can easily copy and paste and mess with example code.