This is true. I know someone with a legal first name that's two words. He's a kid I work with. His parents made a point that his name isn't one or the other, it's both, and we are to address him as such.

To my understanding (as a non-tech person who consumes tech-related media), name fields are commonly culturally biased. Usually it impacts last names, which can vary in size and layout across the world, sometimes including hyphens (which some systems don't like either.) Super short or long names also run into problems. Not everyone has one first name, one middle name, and one last name, but a lot of systems aren't designed to handle that kind of variation.

As a primarily backend engineer, I think the opposite here. The backend makes sense, JS is just a nightmare.

Japan has gotten a lot better but you still run into shit for this sometimes. First and middle names often have to be input without a space, so you end up with Johnwendell Anderson. And sometimes forms require names to be input with the Japanese phonetic alphabet (which lacks a lot of letters in English), and then if it doesn't match some document you need to verify an online input there can be trouble. So Jeeves would become Jiibuzu, and good luck matching that to your passport at the airport.

Or they work for a for-profit company so there's KPIs on how much they go under/over estimate on a task and either someone else did the estimate, or coworkers judge them for conservative estimates, so they did it as quickly as possible