Shine Solutions, an Australian software consultancy, publishes engineering posts on cloud, security, and programming practice.
HN links it mainly for the 'Falsehoods Programmers Believe About Names – With Examples' follow-up, which commenters call helpful for its concrete examples.
Okay but that's a terrible example: lots of people don't have the same last name despite being married. So you better use separate fields for that if you want "last names". But of course, programmers famously have no idea what names are, resulting in a never ending stream of "why the fuck won't you let me use the name that I have?" for anything from ecommerce to government websites, so you really shouldn't even have a separate first and last name field, you should just have a "name" field, and it bloody well better support all of unicode, because the only person who can tell you what their name is, is the person filling out the field, not you as form designer =)
[1] https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
[2] https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/
Yes. AWS biggest advantage now is the giant marketplace of vendors and partners so you can get help and managed services for just about anything.
In my experience, most startups just want managed options they can run themselves rather than engaging partners but if that's what you need then AWS will have more companies to offer, although GCP does have qualified partners. I recommend contacting one of the GCP developer advocates either in this thread or on twitter for help, or email me separately and I'll put you in touch.
Also I havent worked with them but https://shinesolutions.com/ has put out plenty of articles and case studies that seems to show they're pretty capable, that might work for you.
I think on the technical end, if you're serious about writing a valid checklist, it will probably be as easy to write code that does it. And those end up as frameworks, even if it's as simple as https://html5boilerplate.com/
There's a lot of noise out there because of all the consultants trying to do marketing. And while some, like Falsehoods Programmers Believe About Names [1] are actually helpful, the line between what should be acted on and what should be ignored isn't clear.
[1] https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/
https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/ gives examples.
One counter-example for "People have, at this point in time, one full name which they go by." I learned from the 2020 election concerned the Georgia voter fraud claim that someone used the name "James Blalock" to vote, years after he died in January 2006.
Thing is, it was his 96-year-old widow, "Mrs. James Blalock Jr.", who voted. That was the name she registered as, back when using "Mrs. <Husband>" was a common custom.
> I wish there was a similar list: Falsehoods Programmers Believe About Human Names.
There is:
* https://news.ycombinator.com/item?id=18567548
* Points to: https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/
* Which references: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
Also, "A curated list of falsehoods programmers believe in."
* https://github.com/kdeldycke/awesome-falsehood
> nobody's surname needs 128 bytes
I believe that's #6 falsehoods programmers believe about names (with examples)
https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/
Ingoring multi byte characters there are still plenty of long names https://www.ancestry.com/c/ancestry-blog/discovering-the-history-of-long-last-names
If you're going to try for a "reasonable" max name length it would probably need to be at least 4kb.