Martin Fowler

Databricks Lakebase enables Martin Fowler’s long-aspirational Practice #4—“every developer gets their own database instance”—via copy-on-write branching, making evolutionary database development operational at production scale for the first time.

代码验证成为软件开发瓶颈，LLM应用需警惕安全风险，遗留系统现代化是短期价值重点。

DSL和良好抽象能显著提升LLM代码生成的可靠性和可审查性，Martin Fowler推荐该实践。

Harness Engineering和自托管模型在AI开发中变得关键，能减少token使用并提升模型实用性。

DSLs通过明确边界和抽象确保LLMs生成代码的准确性，Tickloom案例展示其与LLMs的协同效应。

代理式开发已进入生产阶段，架构设计仍需关注，token成本成为衡量设计质量的新指标。

LLM技术正在改变编程方式，提升效率并激发创造力，同时对软件开发方法论如DDD提出了新挑战。

Martin Fowler highlights flawed AI usage metrics, historical job displacement by tech, benchmarking differences between closed and open models, and how LLMs amplify code debt and produce low-quality 'AI slop'.

Martin Fowler与Kent Beck讨论了AI在重构复杂代码库中的应用，以及开源、安全、认知耐力、AI对就业的影响和AI监管的现状。

Martin Fowler discussed his experiences with LLM-augmented programming at the GOTO leaders' conference, including case studies by Kent Beck and Ian Johnson.

Martin Fowler proposes multi-stage sensors (coding, integration, continuous monitoring) to enhance AI-generated code maintainability, covering type checking, dependency analysis, security scanning, and more.

Martin Fowler proposes using multiple sensors (dependency-cruiser, Semgrep, mutation testing) to monitor maintainability in real-time during code generation, revealing significant defects in module dependencies and change risks in AI-generated code.

Martin Fowler proposes using an LLM to actively interrogate users to build context for complex tasks.

Martin Fowler shares insights on the role of AI in software development, code migration, and specification validation.

In the era of LLMs, the core value of code has shifted from machine instruction execution to conceptual model design, requiring developers to focus on domain vocabulary and system architecture.

Vibe coding builds software applications by completely ignoring the code generated by LLMs, only developing through prompts and feedback, but poses risks in maintainability, correctness, and security. This technique suits non-programmers creating disposable applications but is unsuitable for production environments.

AI理解代码严重依赖变量名等字面特征，而非语义推断；函数长度不关键，用清晰命名表达意图才是人与AI共读代码的核心原则。

Martin Fowler discusses using various sensors to monitor and improve the maintainability of a codebase, focusing on functional correctness, architectural fitness, and internal quality.

Birgitta Böckeler's exploration shows computational sensors alone are insufficient for effective static code analysis, requiring AI for semantic interpretation and trade-off considerations.

Martin Fowler指出工程与高管层对AI存在认知差异，类比互联网泡沫警告AI过度炒作，但内容碎片化且缺乏技术深度。

Martin Fowler碎片化讨论多个技术话题，但缺乏系统深度，适合快速浏览而非深入学习。

Martin Fowler proposes a new approach to automatically gather context for LLMs.

Martin Fowler discusses whether there will be source code in the future, pointing out that code has two purposes: as machine instructions and a conceptual model of the problem domain.

文章讨论了LLM在编程中的应用、LLM对话的四种类型以及AI领域中不同观点的分歧，但信息密度较低。

AI技术被用于帮助制药研究人员从PDF报告中查询数十年的信息，但文章信息密度较低，缺乏具体机制和深度分析。

The article is a fragmented thought from Martin Fowler about software development, writing without text editors, and using LLMs as functions.

该推文仅为Martin Fowler个人博客‘Fragments’的简短预告，列出若干话题标题（如AI编码指南、harness工程视频、函数长度等），但未提供任何实质性内容或观点。

Martin Fowler转发了一篇关于智能代理中静态分析传感器的初步文章，但原文内容未提供，仅含标题和链接，缺乏技术深度与可验证信息。