QCon London 2026: Refreshing Stale Code Intelligence
AI 搜索 | 作者 industry_watcher | 发布于7 小时前 | | 阅读数：70QCon London 2026: Refreshing Stale Code Intelligence
原文标题: QCon London 2026: Refreshing Stale Code Intelligence
来源: InfoQ | 分类: news
原文链接: QCon London 2026: Refreshing Stale Code Intelligence
📰 中文摘要
QCon London 2026: Refreshing Stale Code Intelligence
[
AI, ML & Data Engineering
](/ai-ml-data-eng/)
QCon London 2026: Refreshing Stale Code Intelligence
Mar 19, 2026
2
Listen to this article - 0:00
Audio ready to play
0:00
0:00
Normal1.25x1.5x
Like
At QCon London 2026, Jeff Smith presented the mismatch between AI coding models and real-world codebases. W...
🔍 内容解读
段落 1
QCon London 2026: Refreshing Stale Code Intelligence
💡 行业趋势：这反映了当前技术发展的前沿方向，值得持续关注其后续进展。
段落 2
QCon London 2026: Refreshing Stale Code Intelligence
💡 行业趋势：这反映了当前技术发展的前沿方向，值得持续关注其后续进展。
段落 3
At QCon London 2026, Jeff Smith presented the mismatch between AI coding models and real-world codebases. While AI tools are helping developers generate code faster than ever, Smith argued that the models themselves are increasingly stale because they lack the repository-specific knowledge required to produce production-ready contributions.
🤖 AI技术解读：这体现了人工智能技术在垂直领域的深入应用，展示了AI如何改变传统行业的工作方式。
段落 5
The presenter described this gap as structural rather than temporary. Most coding models are trained on snapshots of public repositories that may be months old, and they rarely have access to an organization’s internal code. As a result, the models can generate syntactically correct code but often fail to follow the architectural constraints and conventions that govern individual repositories.
🤖 AI技术解读：这体现了人工智能技术在垂直领域的深入应用，展示了AI如何改变传统行业的工作方式。
段落 6
One trend highlighted in the talk is the rapid growth of AI-assisted contributions. Mentions of AI tools in pull requests across several large open source projects increased dramatically between 2022 and 2025. However, acceptance rates have moved in the opposite direction. Smith cited data showing that pull request acceptance dropped during the same period.
🤖 AI技术解读：这体现了人工智能技术在垂直领域的深入应用，展示了AI如何改变传统行业的工作方式。
段落 7
This pattern suggests that AI is increasing the volume of generated code but not necessarily improving the percentage of contributions that can be merged. According to Smith, the fundamental reason is that every repository has its own unwritten rules. These architectural constraints often live in the experience of senior engineers or in patterns embedded in a project’s commit history rather than in formal documentation.
🤖 AI技术解读：这体现了人工智能技术在垂直领域的深入应用，展示了AI如何改变传统行业的工作方式。
段落 8
The talk examined how these rules shape real development workflows. Smith described two broad categories of constraints found across repositories. Architectural rules define how the system itself is structured. These include requirements such as component registration patterns, dependency handling mechanisms, or cross-file version synchronization.
🤖 AI技术解读：这体现了人工智能技术在垂直领域的深入应用，展示了AI如何改变传统行业的工作方式。
📄 完整原文
点击展开查看完整原文
QCon London 2026: Refreshing Stale Code Intelligence [ AI, ML & Data Engineering ](/ai-ml-data-eng/) # QCon London 2026: Refreshing Stale Code Intelligence Mar 19, 2026 2 Listen to this article - 0:00 Audio ready to play 0:00 0:00 Normal1.25x1.5x Like At [QCon London 2026](https://qconlondon.com/), [Jeff Smith](https://qconlondon.com/presentation/mar2026/refreshing-stale-code-intelligence) presented the mismatch between AI coding models and real-world codebases. While AI tools are helping developers generate code faster than ever, Smith argued that the models themselves are increasingly stale because they lack the repository-specific knowledge required to produce production-ready contributions. /filters:no_upscale()/news/2026/03/stale-code-intelligence/en/resources/1heade11-1773895951832.jpg) The presenter described this gap as structural rather than temporary. Most coding models are trained on snapshots of public repositories that may be months old, and they rarely have access to an organization’s internal code. As a result, the models can generate syntactically correct code but often fail to follow the architectural constraints and conventions that govern individual repositories. One trend highlighted in the talk is the rapid growth of AI-assisted contributions. Mentions of AI tools in pull requests across several large open source projects increased dramatically between 2022 and 2025. However, acceptance rates have moved in the opposite direction. Smith cited data showing that pull request acceptance dropped during the same period. This pattern suggests that AI is increasing the volume of generated code but not necessarily improving the percentage of contributions that can be merged. According to Smith, the fundamental reason is that every repository has its own unwritten rules. These architectural constraints often live in the experience of senior engineers or in patterns embedded in a project’s commit history rather than in formal documentation. The talk examined how these rules shape real development workflows. Smith described two broad categories of constraints found across repositories. Architectural rules define how the system itself is structured. These include requirements such as component registration patterns, dependency handling mechanisms, or cross-file version synchronization. Procedural rules govern how code changes are introduced and reviewed. These include pull request conventions, testing expectations, and review workflows. Although experienced contributors quickly learn these patterns, generic coding models typically do not. Smith noted that these rules are often enforced implicitly during code review rather than through automated tools. As a result, AI-generated code can appear correct while still violating repository constraints. To address this problem, Smith proposed repository fingerprinting, systematically identifying and documenting the unique constraints of a codebase. The goal is to extract the implicit rules that developers already know and make them accessible to both humans and AI systems. The presenter also argued that current benchmarks for coding models often fail to measure what actually matters in production environments. Generic tasks such as algorithmic problems or language syntax checks do not capture the repository-specific constraints that determine whether code can be merged. Instead, organizations should evaluate AI coding tools based on their ability to respect the architectural constraints of their own codebases. According to Smith, teams that explicitly document and operationalize their repository rules will have a significant advantage as AI-generated code becomes more prevalent. The talk concluded with the growing mismatch between AI models and real repositories is not primarily a tooling problem but a knowledge management problem. Engineering teams already possess the knowledge required to guide AI-assisted development. The challenge is making that knowledge explicit and integrating it into the systems that generate code. By surfacing the architectural rules embedded in their repositories, organizations can close the gap between generic AI models and the unique requirements of their software systems. ## About the Author **Daniel Dominguez** Show moreShow less ### Rate this Article Adoption Style Author Contacted This content is in the AI, ML & Data Engineering topic Related Topics: Related Editorial Related Sponsors Related Sponsor [ /filters:no_upscale()/sponsorship/topic/614695a5-5e4d-4f5f-9c9a-a9d95f85b864/AkkaWebinarMar26-RSB-1771605862949.jpg) ](/url/f/fd5082e2-7f99-4183-97ea-25b5851231b0/) March 26th, 2026, 11 AM EDT ### Related Content A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. Enter your e-mail address Select your country Select a country I consent to InfoQ.com handling my data as explained in this [Privacy Notice](https://www.infoq.com/privacy-notice).🏢 关于 InfoQ
InfoQ 是知名的技术媒体，专注于报道人工智能、科技创新领域的最新动态。
📎 相关链接
本文内容由 AI 辅助整理，仅供学习交流使用。版权归原作者所有。
图片来源: InfoQ
📷 相关图片
本文地址：http://searchkit.cn/article/15795
