Henry Schuck. Credit: ZoomInfo
There’s a part of this I haven’t seen anyone say out loud. When the person opening the PR gets credit for shipping and the reviewer bears the consequences of reviewing a bad merge, you have a structural problem no tool can solve. That incentive gap widens when the contributor isn’t an engineer building context over time. A PM using an AI coding tool isn’t on a path to owning the service. Unlike a junior engineer who gradually needs less oversight, they’ll need review for every change they make, indefinitely, because they’re not building the kind of context that earns independence. So that review load doesn’t taper but remains a permanent line item, and most teams aren’t planning for it that way.
，这一点在新收录的资料中也有详细论述
AI is ‘stealing information’ from the sources it needs
This behavioral shift creates a new visibility challenge. Your content might rank perfectly on Google, but if it's invisible to AI models when they're formulating answers, you're missing an enormous and growing segment of potential traffic. The users who discover information through AI tools never even see your traditional search rankings because they never visit a search results page.