There are popular arguments that review should be killed outright. Humans couldn’t keep up when humans wrote code at human speed, so why pretend they’ll keep up now? They’re right about the volume problem. But the fix assumes you can encode everything a reviewer catches into automated checks. Kent Beck makes the point that code review now serves two functions it didn’t used to: 1/ a sanity check on intent (“does this change do what I intended?”) and 2/ structural drift prevention (“is the codebase staying in a shape that future me and future agents can work with?”). Both fail silently when reviewers are overwhelmed. Nobody announces “I rubber-stamped this.” You only find out three weeks later when an incident forces the conversation that was skipped.
这意味着，行业在扩张的同时正经历加速洗牌，曾经的蓝海已成红海。
，详情可参考吃瓜
On top of that, purpose-built AI editors like Cursor, Windsurf, and others are attracting serious investment and talent. These aren’t adding AI to an existing editor as an afterthought – they’re building the entire experience around AI workflows. They offer integrated context management, inline diffs, multi-file editing, and agent loops that feel native rather than bolted on.
A first purchase for Southern Brave.