Ben Hughes
2.3K posts


@Pinboard It’s made my favorite cheap dive bar popular with the youth. Nuke it.
English

I really don't know what to make of TikTok. There's this, and then there's the principled argument that banning platforms because of foreign ownership is censorship, and then if you browse r/teachers for a bit it sounds like we should nuke it from orbit.
Dr. Casey Fiesler is no longer on here@cfiesler
I know that not everyone is aware of this - because apparently many of our policymakers 👀 are somehow managing to curate feeds consisting of nothing but teenagers dancing - but some of the very best science communication happening out there right now is on TikTok.
English
Ben Hughes retweetledi

@ndyjohnson “I’m telling you people, there is water. At the bottom of the ocean. They don’t want you to know about the water”
English
Ben Hughes retweetledi

Wrote about why I think prisons and policing need to be radically reformed, but not abolished. TLDR on the latter point: nymag.com/intelligencer/…

English

@skevy @mjackson @spikebrehm The fallacy is thinking that you can create a service so small that you’ll never have to talk to another team and no external event will ever ruin your day.
English

@mjackson @spikebrehm @schleyfox Super-micro microservices are an overreaction, and one that needs to be undone in the industry. But I can't say I'm sad that we don't have to deal with our insane RoR monolith (mostly...) -- that's not the answer either at scale.
English

Counterpoint: Java (Scala) microservices we’re an absolute nightmare for us at Twitter as we migrated off Ruby on Rails. Much of the complexity that Elon mentioned after he bought the company was from this architecture.
Ben Hughes@schleyfox
At @Airbnb, while we appreciated the flexibility of Ruby on Rails earlier on, it absolutely became unsuitable at scale (both traffic and organizationally) and we had to work miracles while replacing much of it with java microservices.
English

@spikebrehm @mjackson I think the real nightmare is scaling development to thousands of engineers (but an important one, involving different tradeoffs than for small teams). We definitely made many mistakes and had a lot of chaos with microservices, but the status quo was also unstable.
English

@mjackson At Airbnb the proliferation of microservices also became an absolute nightmare. But it was more a matter of _how_ we did it, I think — e.g. lack of good tooling, then incentive misalignment with engineers thinking they had to spin up their own service in order to get promoted 🤦🏻♂️
English

At @Airbnb, while we appreciated the flexibility of Ruby on Rails earlier on, it absolutely became unsuitable at scale (both traffic and organizationally) and we had to work miracles while replacing much of it with java microservices.
DHH@dhh
Gotta love the pivot from "it doesn't scale" to "you can't write real systems without types" as the new ding-dong argument against dynamically-typed languages like Ruby (and vanilla JavaScript and Smalltalk and...). rubyonrails.org
English






