This is how we should read hexadecimal
weblogs.asp.net
weblogs.asp.net
Umm that's cool I suppose.
Mainly when I'm reading hex I'm looking for near-null, is it heap, stack or image memory? Those things are useful for me to be able to quickly distinguish and everything else is "calc.exe", "bc" or order-of-magnitude calculations based on number of bits. I do spend a lot of time reading hex, but I'm probably a numeric philistine.
0x4B2AC0AA is forty-eleven giga, twenty-ten mega, twelvety kilo and tenty-ten.
Of course one kilo != 1024, but you get the idea
The best way to read hex is by reading the letters and numbers in order without any added complexity.
able baker charlie dog easy fox
dek el zen tris cat kink
http://ask.slashdot.org/story/03/04/01/0112232/eleventy-what
The number before hundred is quadtwenty tenty nine!
Well, not literally actually. Figuratively actually, like all good translations.
(Note: Not saying it's awkward in an absolute sense, but in the context of a base-twenty system that method of constructing 17-19 fits badly)