Most of the friction people blame on the model is a missing paragraph in the repository. What belongs in a context file, what does not, and why the ones that grow past a page stop working.
The bottleneck moved from writing to reviewing, and the old review habits do not scale to it. Four gates that keep quality without turning one senior engineer into a queue.
One keeps you in the loop at every keystroke, the other takes a task away and brings back a diff. Most teams that argue about which to standardise on end up using both, for reasons that are easy to state.
A coding agent with shell access and repo context is a different tool from an autocomplete. The gains are real and they land unevenly; the cost is that review becomes the bottleneck. What we changed after six months.