Sadly, I would have to decompile the software to make it work on my several Linux workstations, and I have been too lazy to do that (so far).

I got a membrane, backlit Redragon gaming keyboard K512RGB. It is a comfortable keyboard, but I would like to better understand the backlight. It progresses across the keyboard with all the colors of the rainbow. It is pretty but doesn't appear to have a function beyond that. It didn't come with a manual. I liked it well enough that I got another for a machine in my lab.

The older developers worked in a procedural and functional world. A text-based world. When I taught programming for networking and for electrical Engineering in the 2010s, I taught how to think like a programmer, and basic processes. We weren't teaching OOP. I was supposed to teach from a beginner Python book for networking students and beginning C for IC programming for the engineering students. I also added in JavaScript showing the same procedures on web pages. Most of the students liked the web-page exercises better. I did all my programming in person and real time, typos and all, so the students could see that making errors that sunk your program was not the end of the world.

Consistent standards would be nice. I haven't seen any code that included a style guideline, though it might be helpful if the naming convention is complicated.