|
| 1 | +--- |
| 2 | +title: "The Truth About Coding Agents: Why 90% of Your Time Is Now Code Review" |
| 3 | +resourceId: 6 |
| 4 | +date: "2025-11-25" |
| 5 | +--- |
| 6 | + |
| 7 | +This discussion features Beyang Liu, CTO and Co-founder of Sourcegraph, in conversation with a16z, exploring the fundamental shift in software engineering driven by autonomous coding agents like Amp. |
| 8 | + |
| 9 | +### Sourcegraph’s New Agent: Amp |
| 10 | + |
| 11 | +The discussion centers on Sourcegraph's new coding agent, **Amp**, which was built from first principles to leverage the latest "agentic" capabilities of LLMs. Unlike previous tools integrated into existing products, Amp was developed as a standalone agent to fully utilize tool use and reasoning. |
| 12 | + |
| 13 | +* **Two Modes:** Amp operates with two distinct agents: |
| 14 | + * **Smart Agent:** Uses frontier models (like Claude 3.5 Sonnet or GPT-4/5) for complex tasks. It is paid and usage-based. |
| 15 | + * **Fast Agent:** Uses smaller, faster models for targeted edits. Uniquely, this version is **ad-supported**, making it free for hobbyists and casual users. |
| 16 | +* **Optimization:** Sourcegraph moves beyond just "general intelligence" by using specialized sub-agents for specific tasks (e.g., context retrieval, library fetching), often post-training smaller open-source models to handle these specific workflows efficiently. |
| 17 | + |
| 18 | +### The Shift From Coding to Orchestrating |
| 19 | + |
| 20 | +A major theme is the fundamental shift in the software engineer's role. |
| 21 | + |
| 22 | +* **90% Code Review:** As agents like Amp generate more code, the human developer's time shifts from writing syntax to reviewing agent output. This has created a bottleneck, as current code review interfaces (like GitHub PRs) are not designed for reviewing massive, agent-generated changes. |
| 23 | +* **The "Orchestrator" Role:** In the next decade, engineers will function more as orchestrators who manage multiple agents. The human remains essential for "comprehension" and defining the creative intent, but the actual implementation logic is increasingly abdicated to AI. |
| 24 | +* **Loss of "Fun":** Some developers report being more productive but finding the work less enjoyable, as they spend less time building and more time managing and reviewing code. |
| 25 | + |
| 26 | +### The Geopolitics of Open Source Models |
| 27 | + |
| 28 | +Beyang Liu highlights a concerning trend in the AI model landscape: |
| 29 | + |
| 30 | +* **Rise of Chinese Open Source:** The most capable open-weight models for agentic tool use are increasingly coming from Chinese labs (e.g., Qwen, DeepSeek), while US-based open-source efforts are lagging. |
| 31 | +* **Policy Constraints:** The lack of competitive US open-source models is attributed partly to regulatory uncertainty and liability concerns (copyright, safety), which may be making US companies "gun-shy." |
| 32 | +* **Dependency Risk:** There is a risk that global application builders will standardize on Chinese open-weight models if the US ecosystem does not catch up, potentially leading to a long-term technological dependency. |
| 33 | + |
| 34 | +### Philosophy on Agents and Reliability |
| 35 | + |
| 36 | +* **Probabilistic Software:** We are entering an era where we abdicate correctness and logic to stochastic (random/probabilistic) systems. Unlike a database that always returns the same data, an agent "figures out" a problem with varying trajectories. |
| 37 | +* **Evals as Unit Tests:** Evaluations (evals) are useful as smoke tests to prevent regressions, but they shouldn't be the sole optimization target. Real-world product "vibes" and user experience often lag behind static benchmarks. |
| 38 | + |
| 39 | +Full video: <https://www.youtube.com/watch?v=Jxz4GJSG8ZA> |
0 commit comments