 |
| Falsehoods Programmers Believe About Phone Numbers (2016) (github.com) | ||
| recommended by 2 users | 2019 | 451 points by striking | software design | original thread | | ||
| 2 users recommended this thread. What they said: |
| morpheuskafka Feb 24, 2019 | on: Cleave.js – Format input text content when you are typing | context |
|
maaaats Feb 26, 2019 | on: Falsehoods programmers believe about economics (2016) | context
I like these lists, but the ones I like the best are the lists that also provides examples and an explanation with the falsehoods. Pointing out a falsehood without providing a reason does little to change my mind. Falsehoods about phone numbers was recently on HN [0], and I liked how it came with examples. Then it's possible to have a meaningful discussion about each one, and if it is something we need to handle. For instance Phone numbers are always written in ASCII, gives an example where that isn't true. Then we can discuss if that case is meaningful for us to support or not. I cannot build a system that will handle all possible names, emails, addresses, timesystems, currencies, locales or whatnot there is a falsehood article about. So when writing an article like this, if you want it to have impact please explain the point of each bullet. |
Perhaps they should read this: https://news.ycombinator.com/item?id=19214035
Phone numbers are something you dial into a phone. They are not a alphabetic ISO code and then some numbers. Country codes and international dialing codes are NOT 1:1. North Korea for example has two dialing codes but is one county. Many island nations share the US's +1. Staphones have their own dialing prefixes that don't correspond to an ISO country code. With all due respect, this code is a disaster and it is guaranteed to lead to problems when one of these many edge cases is hit.