Why I don't number hexes

So quite a few hex map systems use number hexes, frequently in the format xxyy, where xx is the column, and yy is the row.  I am not a big fan of that for two reasons.

1. It takes up space in every single hex, and further obscures the awesome map-ness.
2. It feels a bit backwards.  Number hexes make sense if you are looking up some common data about a hex, such as if there is a big table that tells you how many ducks can be found in that hex.  Thus there would be an entry for every single hex, many of which would say "No ducks."  But wilderness books don't do that, since that wastes precious page space.  Instead they call out only the hexes that have something interesting in them in the notes.  But now that means the DM is having to look up each hex to see if those numbers match up with something in the booklet.  Hex numbers only make sense if there is something worth saying about every hex.

The approach I am using on the hexbooks is I assume there is about 10-15 interesting locations on any given map.  And so I give a list of numbered blanks on on the map page.  That way the DM or mapper can just write a little number anywhere something interesting is found in the map, and then give it a name.  Someone later using the map can then easily see which hexes have something of interest, and what it is called.  They can then consult the notes for more information.