You can say it in English that way, but if it's already in hex, it often needs to be (or works just as well) in hex as it would in dec, and 0xDEADBEEF, even if you weren't going to call it "Dead beef", is "Ox Dee Eee Aay Dee Bee Eee Eee Eff", compared to "three trillion, seven hundred and thirty five million, nine hundred and twenty eight thousand, five hundred and fifty nine".

Hex in English is shorter in only having an average of 0.265625 syllables per bit, plus one syllable for saying "Ox", compared to 0.875 syllables per bit when expressed in English as above. And when it comes to much shorter values, like single bytes, decimal requires "one hundred and twenty two", seven syllables for 8 bits, compared to "Ox seven Aay" which is only 3 syllables for 8 bits.

People are used to saying values in decimal, but I think most of that is just being used to it, it can actually be easier to just stay in and work in hex entirely when possible, it's actually easier to just not care what the decimal representation is.

Now, I'm not saying when you're writing code you should use hex values that are naturally values that make sense to humans, like int maxNumberOfAttendees = 10;, yeah, that should just be in decimal, it makes sense. But if you're working in color, the idea of converting #AE892B to 11,438,379 is not only unhelpful, it's actively harmful to understanding data. For instance, if you're familiar with color, you can tell that #AE892B is a light brownish color, and #AF002B is a dark-ish red, close to something called "Heritage Red"

But 11,438,379 and 11,468,843 look very close to each other, because when expressed in decimal, the decimal representation hides everything after the first few bits.

But for an extreme example, 65535 and 65536 are just 1 away from each other, and even for someone who works with hex all the time, I might even miss (at a glance) what kind of difference that is. But in hex, it's #00ffff compared to #010000. It's basically bright aqua vs almost perfectly black.