Quoting Andrew Kelley

The Catalyst: Why a 'Smell' Metaphor Resonates in the AI Community When Zig creator Andrew Kelley compared over-reliance on AI-assisted coding to 'smoking,' claiming this 'digital smell' is obvious to non-smokers (those who don't overuse AI), he touched on a sharp, often-avoided contradiction in the current AI wave: the trade-off between efficiency and quality. Simon Willison (a renowned developer and SQLite core contributor) sharing this quote represents a deep-seated concern within the senior engineering community about the proliferation of AI tools. This is no longer a technical discussion about 'whether AI can write code,' but a philosophical examination of 'how AI is changing our code culture.' Deconstruction: What is the 'Digital Smell'? Kelley's core point is vivid. He argues that mistakes made by human developers are typically 'natural' errors like logical oversights or poor handling of edge cases. In contrast, the 'hallucinations' of Large Language Models (LLMs) are different. They generate code that appears plausible and structurally complete but fundamentally violates the project's design philosophy, context, or common sense. This code carries a 'smell'—like over-engineering, unnecessary abstraction, ignoring project-specific conventions, or using 'textbook' patterns that are impractical. For someone like Kelley, who has a strong design philosophy (Zig emphasizes simplicity, transparency, and control), this 'smell' is as pungent as cigarette smoke because it contaminates the purity and consistency of the codebase. Trend Insight: From 'Tool Usage' to 'Cultural Conflict' This incident reveals a deeper trend than technology: AI tools are triggering a cultural fault line within the developer community. On one side are developers embracing 'Agentic Coding,'追求极致开发速度, treating AI as a super external brain. On the other are 'craftsmen' who prioritize code artistry, maintainability, and deep understanding. Kelley's metaphor implies that the code produced by these two cultures is now distinguishable by 'smell.' This isn't just about Code Review; it's a clash of values about what constitutes 'good code.' AI tools may be inadvertently promoting an 'averaged,' soulless code style, which is dangerous for projects striving for excellence (like systems programming languages or critical infrastructure). Practical Value: How Should Developers Navigate This? Kelley's warning isn't anti-AI but sets a boundary—'don't smoke in my house.' For the average developer, the takeaways are: 1. Contextual Usage: Boldly use AI for rapid prototyping, exploratory scripts, or non-core modules to boost efficiency. But for core architecture, security-critical code, or parts that embody a unique design philosophy, you must take the helm and deeply review every line of AI-suggested code. 2. Develop Your 'Sense of Smell': Consciously cultivate the ability to recognize the 'smell' of AI code. This requires reading more high-quality human-written code to understand the 'why' behind it, not just the 'what.' 3. Team Norms: Teams should clarify policies for AI-assisted coding. Which codebases allow its use? Should PR descriptions note AI assistance? During code review, should there be special attention to 'hallucination'-type errors AI might introduce?

Counter-Intuitive/Unexpected: The Cost of Efficiency Might Be the Degradation of 'Craft' An angle that might be overlooked is that over-reliance on AI could lead to a collective degradation of developer 'craft.' Just as the普及 of calculators led to a decline in mental arithmetic, if developers always获取 'correct' code from AI, their ability to solve problems independently, debug deeply, and design creatively might atrophy. What Kelley is defending is precisely this 'craft' that can only be acquired through hands-on practice and deep thinking. He reminds us that AI is a powerful tool, but the user of the tool must maintain dominance; otherwise, the tool will反过来 shape the user. This discussion about 'digital smell' ultimately points to a fundamental question: In the age of AI, what kind of craftsmen do we want to be?