A company with (I'm guessing) less than 2500 developers need to make tens of thousands of merges every day? And they somehow had a team of 7 Claude baby sitters handle this entire thing? I use Claude everyday and I'm predicting this will turn into a major clusterfuck in not too long. Even taking into account the fact that they can burn virtually infinite tokens internally, this will not end well. If I'm wrong, I'll be glad.

  > Engineers are no less valuable, but their work is changing. All of the engineers who worked on this system would now rate Claude as better at writing code than them. But our engineers still supplied the invaluable understanding of the high-level inter-system components and the design-level tradeoffs, making informed choices around the problems we wanted to solve and the scale we knew we needed to achieve. Very often, we found that the role of the engineers was to tell Claude “no.” Agents will sometimes violate core system constraints to satisfy a pattern that should never have been allowed in the first place.

Well that's exactly what "writing" code always meant? It was never about what volume of code you can write. Better at writing code always meant better at writing good code... So how is Claude better than their engineers?

It's incredibly short-sighted to acknowledge that the baby sitters haf to tell Claude no and still not consider what subtle and nasty bugs managed to slip through. Well I guess we'll find out soon enough if that's the case. I'm betting when that's the case.