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.io
What comes after git
Our thoughts about the future of version control
@anthropicai.xmirror.botNew 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.
anthropic.com
Redesigning source control at Anthropic
As our merges per day grew more than tenfold, source control became our biggest development bottleneck. Here, we share how we migrated to an in-house version control system in five months.
