exactly:

Windows doesn't mind little changes in the hardware, a little bit at a time, a new video card, then later a new pci card of whatever. But I did that too even back when I think it was XP. I had build a completely new system, then slapped the hdd with windows on it, then windows had a conniption fit. Telling me, "oh no! I don't think so." waving its finger at me and everything, telling me that if I wanted to use it again, that I'd have to verify that that copy of Windows was actually mine.

that is why, from what I under stand windows uses UUID for.

That UUID is written into the filesystem or swap header by mkfs or mkswap. There are tools that can change it (e.g., tune2fs -U xxxx...), but it is not going to change just by moving the disk around.

Depends on whether that "other" computer has a disk in it as well...

Such as plugging it in via USB and booting it...(as can be done when recovering systems)

The other/internal disk can respond first, and the USB second. In which case the USB is sdb instead of sda.

so putting it in easier terms

the eairly bird gets the worm

I can make my SSD (my boot drive) come up as /dev/sdf if I want to just by switching some wires around after shutting down. On my machine, ALL the drives are spun up and ready within a few seconds of turning it on. With six drives on the same SATA controller, every single time channel 1 gets sda, all the way down to channel 6 having sdf. When I was setting up the SSD, it was plugged into channel 2, therefore it was sdb at the time. I can't speak to having two controllers, since I don't need a second controller... yet.

So yeah, it assigns them in channel order.

But this could be way more information that is needed by OP.