Probably, dd doesn't care. dd does what it is told.
Though there would probably be some weird effects.
If the ISO was on his boot drive, dd might have broken the partition before it finished reading the file.
It's a reference to the Arch Linux fuck-up assessment form anyway.
Shhh let's pretend we are for Groo's sake here.
Although in all seriousness, my desktop has both: a 512 GB NVMe where the OS and apps are installed and a 2 TB 7200 rpm HDD where I dump data and some slower games.
It's insane how much more affordable NVMEs are. When I got my 2tb it was almost three times as much as it is now.
After wiping a backup drive, I decided to only use /dev/disk/{by-id,by-label}/
now, it is longer, but much less error prone.
Though, why formating a partition when it's completely overriden in the very next command. Also you won't be able to boot it anyways, you should flash the entire disk, not a partition.
This is dumb, the is no point in using mkfs just before dding an ISO on a drive, even if it is the wrong one.
That was just an extra step to fit this 4 layer meme format. fdisk -l on the first would have been better instead as others have pointed out.
That, but also the canvas on the last 2 could have just been blank too. It's common in this format, and also makes sense