Benjamin Brittain

Benjamin Brittain

@bwb.dev

Building better systems. ceo ersc.io You might need to put up with an occasional NYC tweet.

462 followers104 following196 posts

Benjamin Brittain reposted

very excited to see this out of A\ this is our thesis at @ersc.io! But we are building a git compatibility layer: ersc.io/blog/what-co... enterprise adoption of new source control is a big ask, so making a smooth bridge from the past to the future is a big part of our offer

ersc.ioWhat comes after gitOur thoughts about the future of version control
Anthropic {bot}@anthropicai.xmirror.bot

New on our Engineering blog: Creating in-house source control. In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.

Benjamin Brittain reposted

Someone just asked "what do you think about this PR?" nice try buddy. That's a distillation attack. Blocked.

Benjamin Brittain reposted

#jj-vcs interoperability with Git continues to be key. The fact that ERSC can swap out the repo storage to not use Git, *and* can have a migration path to a future, better wire protocol than Git's, while preserving compatibility along the way, is amazing!

Steve Klabnik@steveklabnik.com

We've been cooking at @ersc.io "What comes after git" ersc.io/blog/what-co...

Benjamin Brittain reposted

Please welcome to the stand Courts of Contempt—Hell Gate and @typeinvestigations.org new interactive investigation into the machinations of New York's broken judicial system. Secret recordings. Fixed judicial conventions. Sketchy donations. Get ready to dive in. hellgatenyc.com/welcome-to-t...

hellgatenyc.comWelcome to the Courts of ContemptHell Gate and Type Investigations's brand-new deep dive into who actually picks New York's judges, and why it matters.

Benjamin Brittain reposted

I spent an hour today arguing to delay a feature launch, only to realize my fear was a one-way door that existed pre-agents, but now the cleanup project from this category of mistake is much easier. Never ceases to amaze me how radically the assumptions have changed.

I still believe code review is necessary for many reasons, but I don't think I'll be putting code in front of a human without running it through an LLM ever again. It would be inconsiderate to the reviewer not too.

Adam Chalmers@adamchalmers.com

LLM code review is very good now. It's not a substitute for human code review. But it's a useful supplement. It regularly finds things human reviewers miss (and humans also find stuff it misses).

Benjamin Brittain reposted

Replying to @bwb.dev

ben in two hours: > issuing correction on a previous post of mine, regarding former executive teams. you do not, under any circumstances, "gotta hand it to them"

On the bright side, Gateways are a nice improvement.

kat cosgrove@kat.lol

Joint statement from Kubernetes Steering and Security Response Committees: In March 2026, Kubernetes will retire Ingress NGINX, a piece of critical infrastructure for about half of cloud native environments. This is an emergency. Please pay attention. kubernetes.io/blog/2026/01...

Benjamin Brittain reposted

We need to talk about the rise of "smol bean fascism" where you have all the guns and the immunity but the really scary people are the ones with whistles and phone cameras and they're giving you generational trauma and ptsd by filming you killing people for no reason

We're actively looking to grow our team at @ersc.io again! If you are interested or know someone who might be, I'd love to chat. We are looking for distributed storage folk as well as frontend/UX.

Benjamin Brittain reposted

The #tokioconf speakers and talks just got posted: www.tokioconf.com Ticket sales are open! Since it is our first conference, it is hard to estimate how many people will come. We're starting conservative, only 200 tickets right now.

tokioconf.comTokioConf 2026 | Be a Part of Tokio's Official Conference!Join 300+ developers at the inaugural TokioConf 2026 to exchange ideas, learn from one another, and explore the future of async Rust. Hosted by the Tokio Project

We're actively looking to grow our team at @ersc.io again! If you are interested or know someone who might be, I'd love to chat. We are looking for distributed storage folk as well as frontend/UX.

Increasingly a fan of "electric bike" as a LLM analogy, it's a powerful force multiplier. I'm also suspicious of people who only ride electric bikes.

> in fact, volunteering that an LLM has been used to generate work product is to implicitly distance oneself from the responsibility for the content — and serves as to erode the trust that is essential for teamwork. The whole RFD is great, but I particularly related with this line.

Bryan Cantrill@bcantrill.bsky.social

I have put together a (long overdue!) draft RFD on using LLMs at @oxide.computer, but I know that there is a ton more to be said on the topic; thoughts and experiences welcome! rfd.shared.oxide.computer/rfd/0576

Benjamin Brittain reposted

At the risk of starting the flame war to end all flame wars... Modern LLMs (GPT-5.1, Claude 4.5, Gemini 3) produce excellent code and can be a significant productivity boost to software engineers who take the time to learn how to effectively apply them - especially if used with coding agent tools