One of my email addresses is {MyNameKP}@gmail.com. “KP” were just random letters I picked years ago and they don’t mean anything. I also own {MyName}@hotmail.com. Someone once asked why I don’t use {MyName}@gmail.com, so I went home to try to sign up for it, but Gmail said the address already exists. I figured someone else had it and might sell, so I emailed them. Gmail auto-replied that the address doesn’t exist. Why can’t I register an address that isn’t there? Who knows ¯\_(ツ)_/¯
let motherLastName = "Carter Hughes"
let fatherLastName = "Miller Thompson"
let childLastName = "Miller Carter"
let childFullName = "Jean Paul Miller Carter"
Or so that is how it works in many countries around the world.
You might ask, —“Why does the father’s last name go first and the mother’s second?”— That’s an old tradition, and it can change whenever enough people in our society agree. As it stands, the father’s family name tends to persist down the family tree, while the mother’s family name often disappears in each generation.
Or so that is how it works in many countries around the world.
You should have given a more complete example, where the parents themselves have long names to demonstrate that something does have to get dropped when you have children.
My spouse and I grew up in Japan and then moved to America. We have never stopped hating the non-illustrated menus that virtually every restaurant offers. There’s no way to know what you’re really getting. The ingredients don’t really tell you much about the dish you’re going to eat, aside from simple things like steak and similar. Sometimes, restaurants also want to be original and write some mambo jumbo in the menu as if I was interested.
The Americn economy leans heavily on lack of price transparency and opaqueness. You're not allowed to know what you're buying until it delivers, at which point you can either accept it or complain loudly. Adding on a million junk fees and not selling things for prices as advertised is also really important. Food samples would be a huge 180 from all this, culturally speaking.
Gordon Ramsey (in one of his failing restaurant tear-down shows) said that pictures on menus meant the food was shit, and to axe them. He's coming from fine dining, of course, but I couldn't disagree more. Sometimes a lot of the menu is illustrated, but the thing I want to try isn't, so I have to Google it and take a chance.
Pretty much every font I try has one or two things that bug me. I’ve spent the last ten years making my own, first in FontForge, now in Glyphs.app, but it’s incredibly time-consuming. I’ll work on it for a while, then give up for months, delete everything, switch to a different font, use it for a few days, start hating it… and end up back at making my own font again. This cycle repeats pretty much every year.
You’ll probably want to recommend your favourite font, but trust me, I’ve tried all the well-known ones, and they all have their quirks.
> Google Sans Mono was created in 2020 to support contexts that needed fixed-width characters for editorial design, at medium and large text sizes. Despite this, it soon got its first big product integration, replacing Roboto Mono in Google Chat. The only problem? Developers hated it.
[...]
> Recognizing this critical need, a dedicated effort was launched to craft Google Sans Code, a monospaced typeface specifically designed to make code more readable. This involved thorough research into the 20 most common programming languages and how developers interact with code, aiming to make the new coding typeface more visually appealing while reducing the ambiguity of similar-looking letterforms. Based on these insights, Google tasked the Universal Thirst foundry to meticulously focus on specific letters, numbers, and operators to meet these requirements. The result is an eminently readable and surprisingly playful typeface.
> Google Sans Code launched as an open-source font in 2025, and is the typeface used to display code in Gemini.
Curly braces can be really hard to distinguish from parens because they appear in the same sort of place in e.g. JS, and IDEs and highlighters often render them in stupid low-contrast colours. I hate it aesethetically, but I get the usability need.
Hmm, my first reaction was the same as yours. But I have quite bad eyesight and looking at the "regular 400 at 16px" example on the page reminded me that I definitely sometimes find myself squinting trying to work out whether a character is a parenthesis or a brace (Droid Sans Mono). So I suppose it'd probably be quite helpful to have a brace that's very visually distinct from parenthesis even if it's not particularly pretty on its own.
Squishing it down to <12px I can see that problem, even when compared to other good coding fonts like Jetbrains Mono or a font designed for readability like Atkinson Hyperlegible Mono / Next.
Definitely was too quick with my judgement. Still, it just looks really out of place at bigger font sizes and it makes me wonder if there isn't a more elegant solution out there.
i don't have your skills of actually customizing or changing glyphs in fonts directly but i've customized and used scripts to fix glyph characters available as open type features. I've done this for fonts like:
it really is a sickness. a terrible sickness, if you care deeply about fonts. I know you don't care specifically about recommendations, but inevitably i've found myself gravitating to these fonts:
1. Berkeley Mono (paid)
2. SF Mono (walled)
3. Recursive (truly open and legible)
4. Commit Mono
I love the above fonts, but there's a few characters or quirks that drive me bananas on certain days, so inevitably find myself switching between them.
As much as people like to criticize Microsoft Teams, it actually offers a feature called Facilitator [1][2][3] that, to my knowledge, works very well. I say this based on both my own experience and feedback from friends who use it in their day-to-day work.
That said, I, of course, always welcome competition.
Who cares about developer experience? Genuinely asking, because I’m a developer too and I certainly don’t care. What we care about is solving the actual problem of payments with the downstream companies.
DX = developers not shooting themselves in the foot and making it impossible to cancel my free trial because my account got deleted but the autopay didn't
fewers bugs = happier customers not getting charged for shit they didn't agree to be charged for
Basically this. The existing integration paradigm for payments, at its worst, feels like a warehouse filled with footguns on the floor with the lights turned off. Esp for newer developers who are used to more modern devexes which explicitly try to take reasoning about complex state transitions off of your plate.
100% This. I remember joining a billing team that assumed calls to Braintree succeed or fail, so everything was just calling the API as though it was a local function call.
It was great fun debugging the twice annual incidents where the API returned a HTTP500 but charged the customer and created the recurring subscription anyway.
Not to forget we had to scream at them for 6 months to implement 3DS2 on top of their Subscriptions API. Turns out we were the only users of it!
reply