I came into this blog post a hater, but honestly - hats off to the team. This sounds like it was a very arduous project, and I don't envy the engineers that have to sweat over handling Anthropic's scaling commit volume.
To that end though, this line feels like it (intentionally?) undersells the engineering team -
> Very often, we found that the role of the engineers was to tell Claude “no.”
To me, this blog post highlighted the immense value that domain-specific knowledge still carries in engineering. I wouldn't be surprised if their team was comprised of former Facebook/Google/Github source control engineers. Individuals with real experience on these types of systems.
The dream for a lot of folks in the industry right now is that you could just staff a bunch of generalists on a problem like this, and through the power of Claude come up with a sufficient solution. I think the reality is that without the domain expertise to direct Claude, you would end up with something vastly different, and not really usable at Anthropic's scale.
To that end though, this line feels like it (intentionally?) undersells the engineering team -
> Very often, we found that the role of the engineers was to tell Claude “no.”
To me, this blog post highlighted the immense value that domain-specific knowledge still carries in engineering. I wouldn't be surprised if their team was comprised of former Facebook/Google/Github source control engineers. Individuals with real experience on these types of systems.
The dream for a lot of folks in the industry right now is that you could just staff a bunch of generalists on a problem like this, and through the power of Claude come up with a sufficient solution. I think the reality is that without the domain expertise to direct Claude, you would end up with something vastly different, and not really usable at Anthropic's scale.