I suggest trying Windows Subsystem for Linux. You’ll get a simpler way to get familiar with the command line, which is the important part if you’re interested in development.
That or dual boot, you don’t need to set aside a large partition for messing around.
That’s odd! I had no issues with the stock Ubuntu install. Installing CUDA on a Windows machine requires WSL2 now, but I didn’t really use it for anything more than that, so I could’ve just not used it enough to find problems. As soon as I finished the semester that required proprietary software, I got rid of Windows entirely though.
IMO, as long as you get comfortable with the basics like navigating directories and moving files, installing and updating software (first through something like apt, compiling stuff manually isn’t necessary at first), and managing some basic bash settings like aliases, you’re pretty much set. At least, from a programmer’s standpoint.
I dunno how well versed OP is in computers overall is the thing. The above is a good baseline, but you need a general understanding of how operating systems work in general to be really comfortable with something like Arch. Like you gotta know what a driver is before you can troubleshoot issues with your hardware, or if you’re managing disks it’s good to have an idea of how filesystems work. But that all comes with experience.