Orchestrating Claude Code Agents: The Chief of Staff Pattern

i mean its not wrong, basically everyone learns this within a few weeks of actively working with the agentic loop.

but as usual with ai written content, the word bloat is roughly x5 of the words necessary to convey the message - with basically no effort on the meat proxy's part to clean it up in any way, shape of form

Bitter lesson means all these tricks will not be needed in a year or two. Either labs will abstract it in harness or models will become good enough that it can do it by itself

I’ll tell the missing part, what comes next: the team, with teammates and managers, starts making their product decisions. If the user was anywhere near the chat and wrote a mere “ok”, they will be recorded as “user's”.

They will write tests. Lots of tests. Instead of removing any code, there will be 3 layers of backward compatibility, and tests that test presence of tests that test that backward compatibility.

The reviews will find all possible edge cases, including those that can never happen, and make the UI gracefully handle them. With tests.

The diff from any integration PR from team work will be over 10K lines, half of them bureaucracy. Zero chance to review even one – they will churn half-a-dozen per day.

For anything outside of known shape, the original hard topics become quickly displaced with shortcuts and familiar patterns.

Next, the app will break under load, and you will find that it’s caused by a quadratic sweep over the whole DB on any insert to prevent something irrelevant that you specifically told not to do.

You will ask, “wtf? why is it there?”. “It’s load-bearing, you ruled it”.

(That's not a joke. That's how I spent the summer.)