Yeah yeah, we know you're special

https://lemmy.dbzer0.com/post/16500786

Yeah yeah, we know you're special - Divisions by zero

and you shouldn’t be using any of those, since the order can and will change. The numbers are based on the order the devices and device drivers are initialized in, not based on physical location in the system. The modern approach (assuming you’re using udev) is to use the symlinks in /dev/disk/by-id/ or /dev/disk/by-uuid/ instead, since both are consistent across reboots (and by-id should be consistent across reinstalls, assuming the same partitioning scheme on the same physical drives)

This is also why Ethernet devices now have names like enp0s3 - the numbers are based on physical location on the bus. The old eth0, eth1, etc. could swap positions between Linux upgrades (or even between reboots) since they were also just the order the drivers were initialized in.

I’m sure you know this, but to to supplement your comment for future readers, UUIDs are also a good solution for partitions.
I think OP’s point was that UUIDs can still change, but the stuff that makes up the /by-id/ names cannot. Granted, those aren’t applicable to partitions.
How are the uuids going to change unexpectedly?

Depends on your definition of “unexpected”. OP was talking about reinstalls for example, where the root partition is deleted and recreated and its UUID will change as a result. If you copy an fstab from an older system backup you will fail the mount the root partition.

UUIDs can also cause some reverse trouble if you clone them with dd in which case they won’t change but they should, and you end up with duplicate UUIDs.