thoughtFrame

Ciechanowski's work (check Gears and Curves as good examples, but all of them are good) https://ciechanow.ski/archives/

Interactive linear algebra book https://textbooks.math.gatech.edu/ila/

Visualizing quaternions https://eater.net/quaternions

Another quaternions visualization tool that reminded me that a few years ago many sites were full of java applets that were the first "explorables". Sometimes I still stumble upon old university websites that leave some space for the applet but it never loads. Sad stuff

https://quaternions.online/

Some tools to make them:

https://github.com/ManimCommunity/manim

https://p5js.org/

https://processing.org/

As you can see in the other replies, there are many paths that lead to reverse engineering, but I feel like the best way to make the concepts stick is to have "reverse engineer X" be a problem standing in your way (where X is a piece of software, a protocol, etc.) When you have that problem and you need to solve it, you have a target to throw all the "darts" those tutorials give you, and this will probably be more effective than just reading the material and hoping you'll use some of it in the future.

Anyone know what resources developers actually used for programming consoles back in the days of the NES/SNES (and even the PSX)? Nowadays we have a lot of resources and open source games, but it's still pretty hard to make good homebrew. Was it just a matter of the mindset of the time that most programmers don't have anymore?

I'm also curious about this, since in many areas of computing (not only webdev) the old-school guys take some stuff as so obvious that they don't even bother writing about it or explaining it beyond "This is obviously possible, dude". They know how to achieve this level of performance, but for everyone else, we have to cobble together fragmented insights. So if anyone out there reads this and thinks like the GP, please do write about it ;)