Inspired by Falsehoods programmers believe about phone numbers[1] and Falsehoods programmers believe about emails[2].<p>We wanted to share some of the data we have seen from analyzing signups at scale and insights from great companies like Hubspot.<p>It is by no means complete, so please share anything you believe is missing.<p>[1] <a href="https://github.com/google/libphonenumber/blob/master/FALSEHOODS.md">https://github.com/google/libphonenumber/blob/master/FALSEHO...</a>
[2]<a href="https://beesbuzz.biz/code/439-Falsehoods-programmers-believe-about-email" rel="nofollow">https://beesbuzz.biz/code/439-Falsehoods-programmers-believe...</a>
One that continuously comes up at places I work is email validation. Every place I've worked there's someone who want to ensure that users providing "real, valid emails", and no matter how often or clearly I explain why that's a hard problem, I've always seen the team tasked with putting something to attempt it. These days I mostly end up giving the "if you use that ad-hoc validation scheme, you'll block x% of potential signups", and let the business decide if x% is acceptable. That, or I tell them to integrate 3rd party accounts and let people user their google, facebook, or whatever login.