Jed Schmidt

Jed Schmidt

@jed.is

Kingston and Kyoto. Proprietor of https://hasbrouck.house, baritone of https://thefourfives.com.

541 followers159 following6.9K posts

55 years ago, mcdonalds japan decided call their mascot "donald", because they thought it would be easier to pronounce. starting this month he's dropping that name and rebranding as "ronald".

coincidentally, '54 is the year that white castle put air holes in their patties. (they did not charge more for this innovation.)

discovering why my robot lawnmower keeps getting caught in holes around the yard. real datacenter backlash energy here.

rorschached by the barista: 𝔂𝓸𝓾 𝓶𝓪𝓽𝓽𝓮𝓻 vs 𝔂𝓸𝓾𝓻 𝓶𝓸𝓽𝓱𝓮𝓻.

stayed at a new 9hours in tokyo. the capsules now have all sorts of sensors in them, and they send you a sleep report after you checkout.

at an airport dunkin’, where the $6 meal deal is $16.41. at least they honored the promotional digit.

Jed Schmidt reposted

All right, this just came across my radar, and it is *brilliant*. You won't find a better or more compact explanation for [waves hands] all of this. This is the skeleton key.

Brian Hughes@bmhughes.bsky.social

This is actually quite brilliant, up to and including the final sentence 🔥

looking all over for where the soggy bottom boys bust out the chromatic mediant A major chord when i realized what had happened.

forgetting the fact that EN readers are subject to 50% more rules (the last 3 EN rules are basically the last JA rule), interesting that they allow only JA readers to use the bath _before_ drinking.

View full thread

like, before react became popular, there was a lot of overwrought dogma about separation of concerns; it was gauche not to co-locate your scripts, styles, and markup in separate silos. react turned this on its side, prioritizing co-location by component, which always made more sense to me.

in the same way, DO took the cloud silo (ie, network, compute, and storage split into API Gateway, Lambda/EC2, and DynamoDB/S3) and turned it on its side; each object has a bit of all three. this is more natural and also drops ton of config (IAM, et al). i think this innovation is under-appreciated.

one thing i've always thought but never really expressed in a talk (mostly because i don't really do talks anymore) is how durable objects changed the way i think about the backend in much the same way react changed the way i thought about the frontend.